DB2 error written on db2diag.log when TEMS/TEPS services restarts from backup

Technote (troubleshooting)


Problem(Abstract)

The TEPS database marked as being damaged but one sees no problem the TEPS

Symptom

RETCODE : ZRC=0x8602001A=-2046689254=SQLB_BADD "Bad Database, Can't flush"

The error can be shown as:-
2012-11-23-15.11.01.750000+480 I138473402H442 LEVEL: ErrorPID : 7952 TID : 2792 PROC : db2syscs.exeINSTANCE: DB2 NODE : 000 DB : CITICCRMAPPHDL : 0-1173 APPID: 21.28.121.142.37391.12112306584AUTHID : DB2ADMINFUNCTION: DB2 UDB, base sys utilities, sqlesrsp, probe:90DATA #2 : Hexdump, 4 bytes0x04EEA194 : F6FB FFFF ....2012-11-23-15.11.01.750000+480 I138473846H502 LEVEL: ErrorPID : 7952 TID : 2792 PROC : db2syscs.exeINSTANCE: DB2 NODE : 000 DB : CITICCRMAPPHDL : 0-1173 APPID: 21.28.121.142.37391.12112306584AUTHID : DB2ADMINFUNCTION: DB2 UDB, data protection services, sqlpthrd, probe:440RETCODE : ZRC=0x8602001A=-2046689254=SQLB_BADD "Bad Database, Can't flush" DIA8427C The database has been marked as being damaged.

Cause

A portion of SQLB termination processing failed.

Environment

ITM 6.2.1 IF3 AIX 5.3

Diagnosing the problem

DIA8427C The database has been marked as being damaged.

Resolving the problem

Reinstall DB2 or update DB2 version to 9.5 Fp5

Document information


More support for:

Tivoli Monitoring

Software version:

5.3

Operating system(s):

AIX 6.1

Reference #:

1422494

Modified date:

2013-03-08

Translate my page

Content navigation