DB2 - Problem description
Problem IT39142 | Status: Closed |
"PRUNE LOGFILE PRIOR TO" command MAY RESULT IN UNEXPECTED SQLP_EXT_INVALID "INVALID EXTENT HEADER (FILENUMBER OR SIGNATURE IDS). | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Using PRUNE LOGFILE PRIOR TO syntax to free older log files may result in no return error message from command line, but an SQLP_EXT_INVALID "Invalid extent header (filenumber or signature IDs)." could be dumped in db2diag.log and expected log files not being removed. This can happen when log file numbering has wrapped from S9999999.LOG to S0000000.LOG in the past. The message in db2diag.log will be similar to the one below, where, you can see that the extend ID in the dump of the log file header is prefixed with "1" thus making it a 8 digits number instead of a 7 digits number as in the log file name. Thus, as you can see below, when pruning log file prior to S0587741.LOG, in a situation where the log file numbering has wrapped, the extent validation will fail because the extent ID in the log fail header does not match the extent ID of the file name. 2019-01-10-09.33.06.802357+060 I38433A2583 LEVEL: Error PID : 2818316 TID : 3343 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB1 APPHDL : 0-7 APPID: *LOCAL.db2inst1.190110082030 AUTHID : DB2INST1 HOSTNAME: MYHOST1 EDUID : 3343 EDUNAME: db2agent (MYDB1) 0 FUNCTION: DB2 UDB, data protection services, sqlpgoleCheckForInvalidExtentHeader, probe:200 MESSAGE : ZRC=0x071000D4=118489300=SQLP_EXT_INVALID "Invalid extent header (filenumber or signature IDs)." DATA #1 : String, 47 bytes The log file number does not match the request. DATA #2 : String, 41 bytes logStreamId / extNum / callerFlag / XHDR: DATA #3 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes 0 DATA #4 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes 587741 DATA #5 : Hex integer, 8 bytes 0x0000000000000001 DATA #6 : SQLPG_XHDR, PD_TYPE_SQLPG_XHDR, 2048 bytes Validity Check 1 = 8 Format Version = 13 xhdrAlVersion = V:10 R:5 M:0 F:7 I:0 SB:0 Log Extent State = 0x0020a001 - SQLPG_State_Init - SQLPG_State_Force_Archive - SQLPG_State_Closed - SQLPG_State_Logretain Signature = IBMLOG Partition = 0 Log Stream = 0 Topology Life ID = 1462674533 2016-05-08-02.28.53.000000 GMT Compression Mode = 0 (UNCOMPRESSED) Segment Size = 0 Extent Number = 10587741 Extent Size = 2500 Number of Pages = 4 Previous Extent ID = 1547108036 2019-01-10-08.13.56.000000 GMT Database Log ID = 959613951 2000-05-29-15.25.51.000000 GMT Current Extent ID = 1547108037 2019-01-10-08.13.57.000000 GMT firstLso = 107922307506421 maps to 000062A2EA727010 minTruncOffset = 0 fileEntryNum1 = 0 fileEntryNum2 = 0 logFileChainId = 0 lsnBase = 00003513DBBB1BF1 logChainInfo[0] = 0 0000000000000000 1462663869 31585 logChainInfo[1] = 0 0000000000000000 0 0 logChainInfo[2] = 0 0000000000000000 1462663869 31585 logChainInfo[3] = 18446744073709551615 FFFFFFFFFFFFFFFF 4294967295 0 gfaNumEntries = 0 gfa(Global FRALA Array) : idx gfaLogStreamId gfaExtNum (All-zero GFA entries after gfaNumEntries entries are omitted firstLFSInExtent = 10379591369 firstLFSInNextExtent = 10379591387 lastLfsInExtent = 10379591386 lastLsnInExtent = 00003513DBBB1C7E firstRecLso = 107922307506421 hbGroupNextLfsLsn = 0/0000000000000000 hbStreamLastLfsLsn = 0/0000000000000000 hbStreamDiskLso = 0 updateCnt = 8 extPeerEpoch = 0 xhdrCheckSum = 7EB7EC27 expectedCheckSum 7EB7EC27 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Fix in next release * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Fix in next release * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.11.2021 12.08.2022 12.08.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |