DB2 - Problembeschreibung
Problem IC71325 | Status: Geschlossen |
DB HUNG DURING CRASH RECOVERY DUE TO CORRUPTED/NOT FOUND HISTORY FILE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
The following is the snippet of the symptom in db2diag.log: 2010-08-10-10.40.22.084754-240 I108980421A590 LEVEL: Severe PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, oper system services, sqloNLCKInit, probe:100 MESSAGE : ZRC=0x800F00AE=-2146500434=SQLO_NLCK_PATH_ERROR "Unknown" DATA #1 : String, 57 bytes /db1/xxxxx/dbdir/xxxxx/NODE0000/SQL00001/db2rhist.asc DATA #2 : unsigned integer, 4 bytes 1 2010-08-10-10.40.22.371333-240 E108981012A907 LEVEL: Error PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, probe:768 MESSAGE : SQL2161N A damaged recovery history file could not be fixed. The specified action failed. DATA #1 : String, 60 bytes Error parsing history entry: invalid number of fields found. DATA #2 : String, 23 bytes Number of fields read: DATA #3 : signed integer, 4 bytes -1 DATA #4 : String, 32 bytes Expected number of fields read: DATA #5 : signed integer, 4 bytes 24 DATA #6 : Dumped object of size 512 bytes at offset 0, 58 bytes /export/home/xxxxx/sqllib/db2dump/24331.160.000.dump.bin 2010-08-10-10.40.22.376468-240 E108981920A586 LEVEL: Error PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, probe:1142 MESSAGE : SQL2161N A damaged recovery history file could not be fixed. The specified action failed. DATA #1 : <preformatted> Error reading history entry at file offset 1024. 2010-08-10-10.40.22.377027-240 E108982507A560 LEVEL: Warning PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, probe:1147 MESSAGE : ADM8500W DB2 has failed to read from the history file because of a possible data corruption. Ensure that the file exists and is intact. 2010-08-10-10.40.22.378066-240 I108983068A687 LEVEL: Error PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, probe:1152 MESSAGE : SQL2161N A damaged recovery history file could not be fixed. The specified action failed. DATA #1 : String, 18 bytes History File Entry DATA #2 : Dumped object of size 2107648 bytes at offset 632, 58 bytes /export/home/xxxxx/sqllib/db2dump/24331.160.000.dump.bin 2010-08-10-10.40.22.390635-240 I108983756A508 LEVEL: Error PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, database utilities, sqluhUpdate, probe:321 MESSAGE : SQL2161N A damaged recovery history file could not be fixed. The specified action failed. 2010-08-10-10.40.22.391330-240 I108984265A514 LEVEL: Error PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, database utilities, sqluhUpdateSingle, probe:663 MESSAGE : SQL2161N A damaged recovery history file could not be fixed. The specified action failed. 2010-08-10-10.40.22.391919-240 I108984780A555 LEVEL: Severe PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, data management, sqldCommitHistoryEntry, probe:10 MESSAGE : Error commiting history entry, RC = -2161 DATA #1 : Hexdump, 8 bytes 0xFFFFFFFDBBDCFFAC : 0000 0000 0000 0000 ........ 2010-08-10-10.40.22.392444-240 I108985336A635 LEVEL: Severe PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, data management, sqldmpnd, probe:189 MESSAGE : Error executing pending list log record. Trace data: DATA #1 : Hexdump, 24 bytes 0xFFFFFFFC48FF8F30 : FFFF F78F 0000 0DCF 0000 000B 0000 0041 ...............A 0xFFFFFFFC48FF8F40 : 0000 0020 B857 D71B ... .W.. 2010-08-10-10.40.22.392940-240 I108985972A1455 LEVEL: Severe PID : 24331 TID : 160 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: *LOCAL.xxxxx.100810144004 AUTHID : xxxxx EDUID : 160 EDUNAME: db2redom (TESTDB) FUNCTION: DB2 UDB, data management, sqldCriticalSectionEnd, probe:9298 CALLED : DB2 UDB, data management, sqldmpnd RETCODE : ZRC=0xFFFFF78F=-2161 CALLSTCK: [0] 0xFFFFFFFF77B43D98 __1cIsqldmpnd6FpnIsqeAgent_ipcpnJSQdDLP_LSN8_pnPSQdDLD_RECOV_INF O__i_ + 0x1CD0 [1] 0xFFFFFFFF793EC930 __1cIsqlptppl6FpnIsqeAgent__i_ + 0x538 [2] 0xFFFFFFFF794A4FB0 __1cKsqlpRFWppl6FpnIsqeAgent_pnJSQdDLP_DBCB_pnLSQdDLP_TENTRY_pnK SQdDLP_FRAPP_pnKSQdDLP_FRSCB_pnJSQdDLP_LSN8_I_i_ + 0x190 [3] 0xFFFFFFFF794A67BC __1cNsqlpRecDbRedo6FpnIsqeAgent_pnISQdDLP_ACB_pnJSQdDLP_DBCB_pnK SQdDLP_FRAPP_pnLSQdDLP_TENTRY_pnQSQdDLPR_LOGREC_DIS_pnKREDO_INP + 0x12EC [4] 0xFFFFFFFF794A84A0 __1cPsqlprProcDPSrec6FpnKSQdDLPR_PRCB_IpnUSQdDLPR_PR_QdDUEUE_ENT RY__i_ + 0x2B8 [5] 0xFFFFFFFF794B0D6C __1cPsqlpPRecReadLog6FpnIsqeAgent_pnISQdDLP_ACB_pnJSQdDLP_DBCB__ i_ + 0x6EE4 [6] 0xFFFFFFFF7949A084 __1cUsqlpParallelRecovery6FpnIsqeAgent_pnFsqlca__i_ + 0x904 [7] 0xFFFFFFFF77D417C0 __1cbAsqleSubCoordProcessRequest6FpnIsqeAgent__v_ + 0xE8 [8] 0xFFFFFFFF77D757E0 __1cIsqeAgentGRunEDU6M_v_ + 0x708 [9] 0xFFFFFFFF7A7ED588 __1cKsqlzRunEDU6FpcI_v_ + 0xD0 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * If we are in crash recovery, and the sub-agents that are * * doing the parallel recovery encounters a problem such as * * corrupted or not-found history file, this could caused the * * DB hung. * * The db2diag.log should mention about corrupted or not-found * * history file. For more information, please see the "Error * * Description" section above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 fp 3a * **************************************************************** | |
Local-Fix: | |
N/A | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 97 Fix Pack 3a | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 20.09.2010 04.11.2010 07.12.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP3 | |
Problem behoben lt. FixList in der Version |