DB2 - Problem description
Problem IC63988 | Status: Closed |
DURING CRASH RECOVERY DB2 MAY FAIL TO CREATE NEW TRANSACTION LOG FILES WHEN NEEDED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Db2 may fail to create new transaction logs during crash recovery when needed which will cause the crash recovery to fail or hang. Symptom 1: Crash recovery hangs while the following message is being repeatedly written into db2diag.log 2009-01-23-10.10.07.461979-300 I253295078A442 LEVEL: Warning PID : 9142514 TID : 4628 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-52 APPID: *N0.db2inst1.000000000000 AUTHID : db2inst1 EDUID : 4628 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpWriteLR, probe:4770 MESSAGE : Need more active log space. Symptom 2: Crash recovery abends. One way to trigger the problem is to increase LOGSECOND and perform crash recovery. The following is a Signal #11 (SIGSEGV) call stack taken from an AIX trap file: 00002B9DD4B65B3A sqlpgarl + 0x05ae 00002B9DD4B6990D sqlpgasn + 0x0b4b 00002B9DD4B6AF46 sqpLoggrEdu::RunEDU + 0x0052 00002B9DD5D96C34 sqzEDUObj::EDUDriver + 0x00f2 00002B9DD5D96D2B sqlzRunEDU + 0x0023 | |
Problem Summary: | |
DURING CRASH RECOVERY DB2 MAY FAIL TO CREATE NEW TRANSACTION LOG FILES WHEN NEEDED. | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
FIXED IN DB2 V9.7 FP1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.10.2009 16.12.2009 16.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |