DB2 - Problembeschreibung
Problem IC99232 | Status: Geschlossen |
DEBUG DPS CRASH HDRSETEXPLICITSTARTED PROBE:556677 STACK IN DB2DIAG.LOG WHEN HADR DB ACTIVATED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
A stack is written to the db2diag.log file when a HADR database is Activated. This happens on either the Primary or Standby servers. However, the HADR configuration works without problem. The db2diag.log shows: 2014-02-04-11.19.14.384665+000 I22819E2615 LEVEL: Error PID : 4377 TID : 139851915585280 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-78 APPID: *LOCAL.db2inst1.140204111913 AUTHID : DB2INST1 HOSTNAME: db2r105.db2.local EDUID : 37 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetExplicitStarted, probe:556677 DATA #1 : <preformatted> DEBUG DPS CRASH hdrSetExplicitStarted CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x00007F31DB97529F pdLogPrintf + 0x8F [1] 0x00007F31DFC68A07 _Z21hdrSetExplicitStartedP16sqeLocalDatabasebs + 0x57 [2] 0x00007F31DFC77250 _Z13hdrEduStartupP16sqeLocalDatabaseP9sqeBsuEduP14sqlpMasterDbcb bjb19hdrEduStartupActionP5sqlcab + 0x8E0 [3] 0x00007F31DF3CD611 _Z20sqlpCheckToStartHadrP8sqeAgentP16sqeLocalDatabaseP5sqlcabjPb b + 0x781 [4] 0x00007F31DE5E32CE /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x3CAC2CE [5] 0x00007F31DE5DCAED _ZN16sqeLocalDatabase12FirstConnectEP8SQLE_BWARcP8sqeAgentP8sqlo _gmtiiPb + 0x16FD [6] 0x00007F31DE5CCABE _ZN8sqeDBMgr23StartUsingLocalDatabaseEP8SQLE_BWAP8sqeAgentRccP8s qlo_gmtPb + 0x121E [7] 0x00007F31DE584A7A _ZN14sqeApplication13AppStartUsingEP8SQLE_BWAP8sqeAgentccP5sqlca Pc + 0x3CA [8] 0x00007F31DE57BCC4 _ZN14sqeApplication13AppLocalStartEP14db2UCinterface + 0x574 [9] 0x00007F31DE77FBA0 _Z11sqlelostWrpP14db2UCinterface + 0x40 [10] 0x00007F31DE77EA74 _Z14sqleUCengnInitP14db2UCinterfacet + 0x6F4 [11] 0x00007F31DE77D4A2 sqleUCagentConnect + 0x4D2 [12] 0x00007F31DE886F26 _Z18sqljsConnectAttachP13sqljsDrdaAsCbP14db2UCinterface + 0xB6 [13] 0x00007F31DE84C389 _Z16sqljs_ddm_accsecP14db2UCinterfaceP13sqljDDMObject + 0x3B9 [14] 0x00007F31DE841818 _Z17sqljsParseConnectP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCint erface + 0x58 [15] 0x00007F31E260097C _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 0x36C [16] 0x00007F31DE83B84A /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x3F0484A [17] 0x00007F31DE839E09 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x3F02E09 [18] 0x00007F31DE836E89 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x3EFFE89 [19] 0x00007F31DE836A7B _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xEB [20] 0x00007F31DE562351 _ZN8sqeAgent6RunEDUEv + 0x8B1 [21] 0x00007F31DFAC5724 _ZN9sqzEDUObj9EDUDriverEv + 0xF4 [22] 0x00007F31DF32D337 sqloEDUEntry + 0x2F7 [23] 0x0000003C75C079D1 /lib64/libpthread.so.0 + 0x79D1 [24] 0x0000003C754E8B6D clone + 0x6D 2014-02-04-11.19.14.410300+000 I25435E509 LEVEL: Info PID : 4377 TID : 139851915585280 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-78 APPID: *LOCAL.db2inst1.140204111913 AUTHID : DB2INST1 HOSTNAME: db2r105.db2.local EDUID : 37 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduStartup, probe:21152 MESSAGE : HADR Startup has completed. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All DB2 HADR users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW 10.5 Fix Pack 4 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 LUW 10.5 Fix Pack 4 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 07.02.2014 15.09.2014 15.09.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |