DB2 - Problem description
Problem IC86709 | Status: Closed |
ON IA32 PLATFORM(WINDOWS OR LINUX), DATABASE MARKED BAD DUE TO SQLP_BADLSN FOUND | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
On IA32 platforms, due to an internal non-atomic write of a 64 bit value on 32-bit operating systems, an application may 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: 2012-02-16-10.51.27.468000+060 I3684517H548 LEVEL: Severe PID : 2464 TID : 5424 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : SAMPLE APPHDL : 0-26951 APPID: 9.36.30.159.4691.120216094200 AUTHID : SAMPLE03 EDUID : 5424 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:9120 DATA #1 : <preformatted> diff 47, count 47, fromptr 7F4BA03F, CharPtr 7F4BB171, pageLso 1821066137532, LowPageLso 1821066133457 2012-02-16-10.51.27.484000+060 I3685067H541 LEVEL: Severe PID : 2464 TID : 5424 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : SAMPLE APPHDL : 0-26951 APPID: 9.36.30.159.4691.120216094200 AUTHID : SAMPLE03 EDUID : 5424 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:9120 DATA #1 : <preformatted> rc -2028994519, pageByteCount 4076, pageLso 1821066137532 LookForLso 1821066133504, Bp 7F4BA000 2012-02-16-10.51.27.484000+060 I3685610H152 LEVEL: Severe PID:2464 TID:5424 NODE:000 Title: SQLP_LFPB Dump File: c:\DB2\2464.5424.000.dump.bin 2012-02-16-10.51.27.515000+060 I3685764H1085 LEVEL: Error PID : 2464 TID : 5424 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : SAMPLE APPHDL : 0-26951 APPID: 9.36.30.159.4691.120216094200 AUTHID : SAMPLE03 EDUID : 5424 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:2510 DATA #1 : <preformatted> -2028994519 when reading LSO 1821066133504 from log file S0090067.LOG dpsAgtCbFlags 0 setSkipOutputBuf 0 CALLSTCK: [0] 0x6CD37526 pdLogPrintf + 0x2F8 [1] 0x6F2A0C88 _VInfreq_?sqlpgrlgYAHPAVsqeAgentI_KIPADPAUSQLO_MEM_POOLPAUSQLP_L RHPAPADZ + 0x24C [2] 0x6E146D9F sqlpReadLogForCC + 0x97 [3] 0x6D72B35C sqldGetCurrentlyCommitted + 0x13E [4] 0x6EF49063 _VInfreq_?sqldReadNormYAHPAUSQLD_DFM_WORKHZ + 0x56F [5] 0x6D728665 sqldfrd + 0xF09 [6] 0x6D727859 sqldfrd + 0xFD [7] 0x6D6B560A sqldRowFetch + 0x358 [8] 0x6E498B53 sqlritaSimplePerm + 0xAB [9] 0x6E495471 ?sqlriunn.@@YAHPAUsqlrr_cb@@PAUsqlri_stob@@@Z + 0x23D 2012-02-16-10.51.27.875000+060 I3686851H1026 LEVEL: Severe PID : 2464 TID : 5424 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : SAMPLE APPHDL : 0-26951 APPID: 9.36.30.159.4691.120216094200 AUTHID : SAMPLE03 EDUID : 5424 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:2510 DATA #1 : <preformatted> HeadLsn 000001AA10530CBE, reqlso 1821066133504 CALLSTCK: [0] 0x6CD37526 pdLogPrintf + 0x2F8 [1] 0x6F2A0CDA _VInfreq_?sqlpgrlgYAHPAVsqeAgentI_KIPADPAUSQLO_MEM_POOLPAUSQLP_L RHPAPADZ + 0x29E [2] 0x6E146D9F sqlpReadLogForCC + 0x97 [3] 0x6D72B35C sqldGetCurrentlyCommitted + 0x13E [4] 0x6EF49063 _VInfreq_?sqldReadNormYAHPAUSQLD_DFM_WORKHZ + 0x56F [5] 0x6D728665 sqldfrd + 0xF09 [6] 0x6D727859 sqldfrd + 0xFD [7] 0x6D6B560A sqldRowFetch + 0x358 [8] 0x6E498B53 sqlritaSimplePerm + 0xAB [9] 0x6E495471 ?sqlriunn.@@YAHPAUsqlrr_cb@@PAUsqlri_stob@@@Z + 0x23D 2012-02-16-10.51.28.125000+060 I3696872H559 LEVEL: Severe PID : 2464 TID : 5424 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : SAMPLE APPHDL : 0-26951 APPID: 9.36.30.159.4691.120216094200 AUTHID : SAMPLE03 EDUID : 5424 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data management, sqldRowFetch, probe:666 RETCODE : ZRC=0x87100029=-2028994519=SQLP_BADLSN "Invalid LSN value." DIA8538C An invalid log sequence number (LSN), the value was "". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of CURRENTLY COMMITTED syntax on 32 bit platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
Local Fix: | |
Set database parameter CUR_COMMIT to DISABLED | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 10.1 fix pack 2. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.09.2012 20.12.2012 20.12.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |