db2readlog API fails with SQLP_BADLOG "LOG FILE CANNOT BE USED"
ON LOG EXTENT
db2diag.log shows:
2014-07-05-11.54.58.835760-240 I352291935A488 LEVEL: Info
PID : 8388656 TID : 4371 KTID :
15269961
PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
HOSTNAME: shadowsvt
EDUID : 4371 EDUNAME: db2lfr.0 (SHADOW1)
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:1
DATA #1 : <preformatted>
LFR Scan Num = 569930
LFR Scan Caller's EDUID = 20680
Opening extent 1756 on log stream 0.
2014-07-05-11.54.58.841767-240 I352292424A2622 LEVEL: Error
PID : 8388656 TID : 20680 KTID :
24313999
PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-63532 APPID: *LOCAL.svtdbm.140705155327
AUTHID : SVTDBM HOSTNAME: shadowsvt
EDUID : 20680 EDUNAME: db2shred (SHADOW1)
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:7000
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File
cannot be used"
DIA8414C Logging can not continue due to an error.
DATA #1 : String, 66 bytes
last record from this extent does not match lastLfsLsn in its
XHDR
DATA #2 : unsigned integer, 8 bytes
73612755649
DATA #3 : unsigned integer, 8 bytes
73612755649
DATA #4 : unsigned integer, 8 bytes
73612755649
DATA #5 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
1755
DATA #6 : LFS/LSN, PD_TYPE_SQLP_LFS_LSN_PAIR, 16 bytes
20142006/0000000011888191
DATA #7 : LFS/LSN, PD_TYPE_SQLP_LFS_LSN_PAIR, 16 bytes
20142007/0000000011888198
DATA #8 : SQLPG_XHDR, PD_TYPE_SQLPG_XHDR, 2048 bytes
Validity Check 1 = 8
Format Version = 13
alVersion = V:10 R:5 M:0 F:4 I:0 SB:0
Log Extent State = 0x00208001
- SQLPG_State_Init
- SQLPG_State_Closed
- SQLPG_State_Logretain
Signature = IBMLOG
Partition = 0
Log Stream = 0
Topology Life ID = 1397274152
2014-04-12-03.42.32.000000 GMT
Compression Mode = 0 (UNCOMPRESSED)
Segment Size = 0
Extent Number = 1755
Extent Size = 10240
Number of Pages = 10240
Previous Extent ID = 1404561244
2014-07-05-11.54.04.000000 GMT
Database Log ID = 1397274152
2014-04-12-03.42.32.000000 GMT
Current Extent ID = 1404561298
2014-07-05-11.54.58.000000 GMT
firstLso = 73571017409 maps to 0000001136B10010
minTruncOffset = 0
fileEntryNum1 = 0
fileEntryNum2 = 0
logFileChainId = 0
lsnBase = 0000000011870D7E
logChainInfo[0] = 0 0000000000000000 1397274152 21104
logChainInfo[1] = 0 0000000000000000 0 0
logChainInfo[2] = 0 0000000000000000 1397274152 21104
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 = 20133829
firstLFSInNextExtent = 0
lastLfsInExtent = 20142007
lastLsnInExtent = 0000000011888198
firstRecLso = 73571041095
hbGroupNextLfsLsn = 0/0000000000000000
hbStreamLastLfsLsn = 0/0000000000000000
hbStreamDiskLso = 0
updateCnt = 8
xhdrCheckSum = 76A682EF expectedCheckSum 76A682EF
==
Stack Trace show:
<StackTrace>
-------Frame------ ------Function + Offset------
0x0900000000850154 pthread_kill + 0xD4
0x090000002F62031C ossPthreadKill__FCUiT1 + 0x5C
0x090000002F620458 sqloDumpEDU + 0xD8
0x090000002F467094 sqle_panic__Fi + 0x314
0x090000002F46795C sqlePanicOnDebugBuildOrIfSleepOn__Fv + 0x1C
0x09000000354FC860 sqlpshrEdu__FP8sqeAgentP5sqlcaPv + 0x6420
0x090000003A0F0F30 sqleSubCoordProcessRequest__FP8sqeAgent +
0x250
0x090000002F8B043C RunEDU__8sqeAgentFv + 0x39C
0x090000002F86D07C EDUDriver__9sqzEDUObjFv + 0x23C
0x090000002F86D3BC sqlzRunEDU__FPcUi + 0x3C
0x090000002F62DA14 sqloEDUEntry + 0x7B4
</StackTrace>
The db2diag.log can also show error messages like:
2014-05-15-21.08.01.795190-240 E66408744A817 LEVEL:
Severe
PID : 3604938 TID : 189547 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-2121 APPID:
*LOCAL.db2inst1.140626102013
AUTHID : DPROP1 HOSTNAME: efkxdb21n11
EDUID : 189547 EDUNAME: db2shred (SAMPLE) 0
FUNCTION: DB2 UDB, recovery manager, sqlpshrBuildRecord,
probe:1040
MESSAGE : ZRC=0x87100027=-2028994521=SQLP_TRECTYPERR
"A record other than those expected has been read
during abort"
DIA8536C A bad record type was encountered.
DATA #1 : SQLP_LRH, PD_TYPE_SQLP_LRH, 64 bytes
recLfs 0 recLsn 0000000000000000 lrecsize 0 lrectype 0000
lrecflags 0000
backlso 175923169067008 maps to pso 0000A0C9499C030F thistid
000001369E7E
>><<
2014-05-15-21.08.01.798617-240 I66410248A615 LEVEL: Error
PID : 3604938 TID : 189547 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-2121 APPID:
*LOCAL.db2inst1.140626102013
AUTHID : DPROP1 HOSTNAME: efkxdb21n11
EDUID : 189547 EDUNAME: db2shred (SAMPLE) 0
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:45350
MESSAGE : ZRC=0x87100027=-2028994521=SQLP_TRECTYPERR
"A record other than those expected has been read
during abort"
DIA8536C A bad record type was encountered.
2014-05-15-21.08.01.803275-240 I66410864A1520 LEVEL: Error
PID : 3604938 TID : 173413 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-2121 APPID:
*LOCAL.db2inst1.140626102013
AUTHID : DPROP1 HOSTNAME: efkxdb21n11
EDUID : 173413 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, recovery manager,
sqlpshrValidateLogStreamEndPoint, probe:1130
MESSAGE : ZRC=0x87100027=-2028994521=SQLP_TRECTYPERR
"A record other than those expected has been read
during abort"
DIA8536C A bad record type was encountered.
DATA #1 : <preformatted>
Forward phase of recovery on stream 0 did not reach end of logs. |
