|
Problem IC68427
|
Status: Geschlossen |
SIGNAL #11 CRASH OR HIGH CPU USAGE WHEN IPV6 CLIENT CONNECTED. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
When an IPv6 client is connected to the database and LIST
APPLICATIONS is executed a segmentation fault/access violation
will cause the server to crash with a stack similar to the one
below:
ossDumpStackTraceEx
OSSTrapFile
sqlo_trce
sqloEDUCodeTrapHandler
sqeAppTable
sqlmonssagntj
sqlmonssbackend
sqlesrvr
sqleMappingFnServer
sqlerKnownProcedure
sqlerCallDLP
sqljs_ddm_excsqlstt
sqljsParseRdbAccessed
...
...
</StackTrace>
Other symptoms may include 100% CPU usage or hang. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See ERROR DESCRIPTION. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v9.7 Fixpack 3. *
**************************************************************** |
| Local-Fix: |
Revert clients to IPv4 |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in v9.7 Fixpack 3. At minimum this fix should be
applied to the server. |
| Workaround |
See LOCAL FIX. |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC68428 IC68429
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 05.05.2010
10.01.2011
10.01.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP3
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
