DB2 - Problem description
Problem IC97599 | Status: Closed |
CRASH RECOVERY FAIL WHEN FREEING DELETE PENDING EXTENTS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
In rare condition, Crash recovery is failing when freeing delete pending extents db2diag.log is showing the following: 2013-11-05-14.14.58.030000+060 I41604F509 LEVEL: Warning PID : 2580 TID : 4028 PROC : db2syscs.exe INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: 127.0.0.1.2237.131105131438 AUTHID : db2inst1 EDUID : 4028 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410 MESSAGE : Crash recovery started. LowtranLSN 000001412BE0A4D4 MinbuffLSN 000001411F37A40A 2013-11-05-14.14.58.046000+060 E42115F462 LEVEL: Warning PID : 2580 TID : 4028 PROC : db2syscs.exe INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: 127.0.0.1.2237.131105131438 AUTHID : db2inst1 EDUID : 4028 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410 MESSAGE : ADM1530E Crash recovery has been initiated. 2013-11-05-14.14.58.046000+060 I42579F536 LEVEL: Warning PID : 2580 TID : 4028 PROC : db2syscs.exe INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: 127.0.0.1.2237.131105131438 AUTHID : db2inst1 EDUID : 4028 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:1182 MESSAGE : numWOCB set to DATA #1 : Hexdump, 8 bytes 0x000000001A9568F0 : 8000 0000 0000 0000 ........ 2013-11-05-14.14.58.061000+060 I43117F506 LEVEL: Warning PID : 2580 TID : 4028 PROC : db2syscs.exe INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: 127.0.0.1.2237.131105131438 AUTHID : db2inst1 EDUID : 4028 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000 DATA #1 : <preformatted> Using parallel recovery with 3 agents 59 QSets 177 queues and 64 chunks 2013-11-05-14.14.58.077000+060 E43625F501 LEVEL: Warning PID : 2580 TID : 11044 PROC : db2syscs.exe INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: 127.0.0.1.2237.131105131438 AUTHID : db2inst1 EDUID : 11044 EDUNAME: db2redom (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpParallelRecovery, probe:880 DATA #1 : <preformatted> Resetting max shredder memory to 14509152 from 18124800 2013-11-05-14.15.08.842000+060 I44128F623 LEVEL: Warning PID : 2580 TID : 11044 PROC : db2syscs.exe INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: 127.0.0.1.2237.131105131438 AUTHID : db2inst1 EDUID : 11044 EDUNAME: db2redom (SAMPLE) 0 FUNCTION: DB2 UDB, buffer pool services, sqlbRedoFreeExtents, probe:820 DATA #1 : String, 70 bytes Informational: Redoing FREE_PENDDEL but no extents are pending delete. DATA #2 : Hexdump, 8 bytes 0x000000045F1FA348 : 0605 0F00 0040 FD00 .....@.. 2013-11-05-14.15.08.858000+060 I44753F507 LEVEL: Warning PID : 2580 TID : 11044 PROC : db2syscs.exe INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: 127.0.0.1.2237.131105131438 AUTHID : db2inst1 EDUID : 11044 EDUNAME: db2redom (SAMPLE) 0 FUNCTION: DB2 UDB, RAS/PD component, pdEDUIsInDB2KernelOperation, probe:600 DATA #1 : String, 19 bytes sqlbRedoFreeExtents DATA #2 : String, 4 bytes sqlb and trap file: Exception C0000005 Occurred Exception Address = 0000000001D1B1A0 <sqlpCopyLsn> <C:\db2_v97fp8\ntx64\s130316\engn\include\sqlpglob.h:714> <sqlbReduceLastInitSMPExtent> <sqlbSMP.C:4510> <sqlbFindNewHighWaterMark> <sqlbSMP.C:4077> <sqlbRedoFreeExtents> <sqlblog.C:895> <sqlbRedo> <sqlblog.C:4032> <sqldmrdo> <sqldmrdo.C:875> <sqlpRecDbRedo> <sqlprfwd.C:2336> <sqlprProcDPSrec> <sqlprfwd.C:4368> <sqlpPRecReadLog> <sqlprfwd.C:6492> <sqlpParallelRecovery> <sqlprecm.C:1503> <sqleSubCoordProcessRequest> <sqlescgt.C:1006> <sqeAgent::RunEDU> <sqle_agent.C:3983> <sqlzRunEDU> <sqlz_edu_obj.C:35> <sqloEDUEntry> <sqloedu.C:3456> | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * See Error Description * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB 10.1 for Linux, Unix, and Windows Fix Pack 4 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB 10.1 for Linux, Unix, and Windows Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.11.2013 08.04.2014 08.04.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |