DB2 crashes every couple of days. When the DB2 server is recycled, everything will work for a couple of days before it crashes again.
DB2 continually crashes.
TPC database corruption.
Diagnosing the problem
The following highlights some of the errors that are logged by DB2 causing database corruption. You might notice errors similar to the ones listed below being logged in the db2diag.log file:
This error may indicate index corruption and/or index or data inconsistency issues
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data Page"
DIA8500C A data file error has occurred, record id is "".
These are indications of log corruption, bad log records, or a bad page on disk
RETCODE: ZRC=0x86020019=-2046689255=SQLB_CSUM "Bad Page, Checksum Error"
DIA8426C A invalid page checksum was found for page "".
The CBIT error is indicative of (hardware errors) a potential disk issue
2007-07-09-22.214.171.1246176+120 I16992C16377 LEVEL: Severe
PID : 68098 TID : 1 PROC : db2agent (sample)
INSTANCE: instest NODE : 000 DB : sample
APPHDL : 0-635 APPID: *LOCAL.instest.070709082609
FUNCTION: DB2 UDB, buffer pool services, sqlbcres, probe:20
MESSAGE : Important: CBIT Error
DATA #1 : Hexdump, 4096 bytes
Resolving the problem
If database corruption is suspected, the recommendations are as follows:
1) Seek assistance from DB2 support team.
2) Restore the database from a known good database backup.
|Storage Management||Tivoli Storage Productivity Center Basic Edition||Windows, AIX, Linux||All Editions|