Issue

• The following is reported in systemlogs:

"Bad Page, Checksum Error" seems to be on Jan 7 around 5:11pm (see var/log/mssages.4) :

[...] DB2[24266]:  2013-01-02-17[..] LEVEL: Severe PID     :
[...] FUNCTION: DB2 UDB, buffer pool services, sqlbVerifyCBITS, probe:1110 MESSAGE : 
[...] SQLB_CSUM "Bad Page, Checksum Error" [...] A invalid page checksum was found for page "". 
[...] DATA #1 : String, 64 bytes Error encountered trying to read a page - information follows :  
[...] DATA #2 : String, 95 bytes CBIT verification error bitExpected is 1, userByte is 48, sector 7 
[...] (from head of page, 0 based)
[...] DATA #3 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes 
[...] DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC,
88 bytes     Obj: {pool:3;obj:532;type:0} Parent={3;532}   lifeLSN: [...]  tid:

[...] DB2[24266]:  2013-01-02-17[..]       LEVEL: Critical
[...] FUNCTION: DB2 UDB, buffer pool services,
sqlbLogReadAttemptFailure, probe:10 MESSAGE : ADM14001C  An unexpected and critical error has occurred:
"BadPage".            The instance may have been shutdown as a result. "Automatic" FODC            (First
Occurrence Data Capture) has been invoked and diagnostic            information has been recorded in directory
"/path/dir". Please look in this
directory for detailed evidence            about what happened and contact IBM support if necessary to diagnose
the problem.

An IBM white paper on this topic at http://www.ibm.com/developerworks/data/library/techarticle/dm-1208corruptiondb2/index.html