DB2 - Problembeschreibung
Problem IC63030 | Status: Geschlossen |
DB2 INSTANCE MAY CRASH WHEN EVENT MONITOR WAS SHUTTING DOWN. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
DB2 instance may crash when event monitor was shutting down, e.g. during the course of shutting down a database. At the time event monitor was collecting each application's monitor info, however sometimes it may refer some NULL pointer and this will incur the crash. In db2diag.log you would see error messages as follows: 2000-01-01-01.01.01.123456+123 I123456789H123 LEVEL: Error PID : 1234 TID : 123 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : OPD APPHDL : 0-1234 APPID: *LOCAL.DB2.012345678901 FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:1 MESSAGE : Error in agent servicing application with coor_node: DATA #1 : Hexdump, 2 bytes 0x5CC3EDD6 : 0000 .. ................................................................ .... 2000-01-01-01.01.01.223456+123 I123456789H123 LEVEL: Error PID : 1234 TID : 123 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : OPD APPHDL : 0-1234 APPID: *LOCAL.DB2.080724203523 FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:10 MESSAGE : Error in agent servicing application with APPLICATION NAME: DATA #1 : Hexdump, 8 bytes 0x01DAC722 : 6462 3265 7665 6E74 db2event | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users of V9.7 on Linux, Unix and Windows platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 instance may crash when event monitor was shutting down, * * e.g. during the course of shutting down a database. * * At the time event monitor was collecting each application's * * monitor info, however sometimes it may refer some NULL * * pointer and this will incur the crash. * * * * In db2diag.log you would see error messages as follows: * * 2000-01-01-01.01.01.123456+123 I123456789H123 LEVEL: * * Error * * PID : 1234 TID : 123 PROC : * * db2syscs.exe * * INSTANCE: DB2 NODE : 000 DB : OPD * * APPHDL : 0-1234 APPID: * * *LOCAL.DB2.012345678901 * * FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, * * probe:1 * * MESSAGE : Error in agent servicing application with * * coor_node: * * DATA #1 : Hexdump, 2 bytes * * 0x5CC3EDD6 : 0000 .. * * .............................................................. * 2000-01-01-01.01.01.223456+123 I123456789H123 LEVEL: * * Error * * PID : 1234 TID : 123 PROC : * * db2syscs.exe * * INSTANCE: DB2 NODE : 000 DB : OPD * * APPHDL : 0-1234 APPID: * * *LOCAL.DB2.080724203523 * * FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, * * probe:10 * * MESSAGE : Error in agent servicing application with * * APPLICATION NAME: * * DATA #1 : Hexdump, 8 bytes * * 0x01DAC722 : 6462 3265 7665 6E74 * * db2event * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB Version 9.7 FixPak 1 or higher levels. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 UDB Version 9.7 FixPak 1. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.09.2009 17.12.2009 17.12.2009 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7. | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |