On IA32 platforms, due to a rare race condition, an internal
64bit value might be assigned only half
its byte value. This will cause an application to fail with
the error "SQL1034C The database is damaged...".
You can find SQLP_BADLSN error in db2diag.log. The following is
a snippet of db2diag.log:
EDUID : 1234 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, data protection services, sqlpgrlg,
probe:9120
DATA #1 : <preformatted>
diff 3043, count 3043, fromptr 0x374f6bf3, CharPtr 0x374f7017,
pageLso 236223202312, LowPageLso 236223198237
...
EDUID : 1234 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, data protection services, sqlpgrlg,
probe:2510
DATA #1 : <preformatted>
-2028994519 when reading LSO 236223201280 from log file
S0001234.LOG dpsAgtCbF
lags 0 setSkipOutputBuf 0
CALLSTCK:
[0] 0xB4AAB503
_Z8sqlpgrlgP8sqeAgentjyjPcP13SQLO_MEM_POOLP8SQLP_LRHPS1_ + 0x623
[1] 0xB5D330CC
_Z16sqlpReadLogForCCP8sqeAgentyjPcP13SQLO_MEM_POOLP8SQLP_LRHPS1_
+ 0x92
[2] 0xB51575A4 _Z25sqldGetCurrentlyCommittedP13SQLD_DFM_WORKy
+ 0x136
[3] 0xB4CA6C46 /home/db2inst/sqllib/lib32/libdb2e.so.1 +
0x1834C46
[4] 0xB4CA703A /home/db2inst/sqllib/lib32/libdb2e.so.1 +
0x183503A
[5] 0xB68DF33B /home/db2inst/sqllib/lib32/libdb2e.so.1 +
0x346D33B
[6] 0xB68DDE83 _Z8sqlischfP7SQLI_CBtj + 0x2E9
[7] 0xB68DAD99
_Z7sqlirdkP8sqeAgentP10SQLI_IXPCRP9SQLD_IXCByP8SQLD_KEYP12SQLI_K
EYDATAP9sqli_scanPi
+ 0x79F
[8] 0xB683FA48 _Z14sqldIndexFetchP8SQLD_CCBP8SQLZ_RID + 0x152
[9] 0xB683D2EF
_Z12sqldRowFetchP8sqeAgentP8SQLD_CCBjjPP10SQLD_VALUEP8SQLZ_RIDjP
12SQLD_ID_LISTP9SQLP_LSN8
+ 0x2E9
...
EDUID :1234 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, index manager, sqliLockUncond, probe:2573
RETCODE : ZRC=0x87100029=-2028994519=SQLP_BADLSN "Invalid LSN
value."
DIA8538C An invalid log sequence number (LSN), the
value was "". |
