ADM7518C "DatabaseAliasName" marked bad

[s***@hcl.in]

Hi,

We are using below given db2
DB21085I Instance "db2inst1" uses "32" bits and DB2 code release "SQL08021"
with level identifier "03020106".
Informational tokens are "DB2 v8.1.0.80", "s041221", "MI00099", and FixPak "8".
Product is installed at "/opt/IBM/db2/V8.FP8".


Suddenly in our UAT environment our databases went bad, the diagnostic logs gives the below given:

db2diag -g db=SCBCESD2,instance=db2inst1 -time 2007-09-05-12.16.26.230520


2007-09-05-13.49.13.194660+480 E3921708027G377 LEVEL: Severe
PID : 15232 TID : 3007072768 PROC : db2agent (SCBCESD2)
INSTANCE: db2inst1 NODE : 000 DB : SCBCESD2
APPHDL : 0-12 APPID: GA14A916.I2D8.0FDE55054913
FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, probe:10
MESSAGE : ADM7518C "SCBCESD2" marked bad.


2007-09-05-13.49.13.191076+480 I3921706701G467 LEVEL: Severe
PID : 15232 TID : 3007072768 PROC : db2agent (SCBCESD2)
INSTANCE: db2inst1 NODE : 000 DB : SCBCESD2
APPHDL : 0-12 APPID: GA14A916.I2D8.0FDE55054913
FUNCTION: DB2 UDB, data protection, sqlpgint, probe:3640
RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"
DIA8526C A fatal error occurred in data protection services.



SQL1224N A database agent could not be started to service a request, or was
terminated as a result of a database system shutdown or a force command.
SQLSTATE=55032


Can you suggest what could be the reason for getting this kind of problem.
Now we are not able to get connection from these databases. It happens for two related databases.

Also please suggest any recovery procedures from this kind of problems.

Thanks

[s***@hcl.in]

Some more info from diaglogs about this issue:

2007-07-12-18.39.01.737861 Instance:db2inst1 Node:000
PID:6582(db2agent (SCBCESD2)) TID:3007072768 Appid:GA14A916.B386.0F0122103740
data management sqldEscalateLocks Probe:2 Database:SCBCESD2

ADM5500W DB2 is performing lock escalation. The total number of locks
currently held is "40964", and the target number of locks to hold is "20482".

====================================================================================
2007-09-05-12.49.17.749032 Instance:db2inst1 Node:000
PID:3775(db2agent (SCBCESD2)) TID:3007072768 Appid:GA14A916.I589.022D24071913
data management sqldEscalateLocks Probe:3 Database:SCBCESD2

ADM5502W The escalation of "40936" locks on table "EXIMUSER.SEC_FAP_RULE" to
lock intent "S" was successful.
^^
2007-09-05-13.05.06.636367 Instance:db2inst1 Node:000
PID:12139(db2agent (SCBCESD2)) TID:3007072768 Appid:GA14A916.PAD3.036AF5050506
base sys utilities sqleMarkDBad Probe:10 Database:SCBCESD2

ADM7518C "SCBCESD2" marked bad.

================================================================================

Max storage for lock list (4KB) (LOCKLIST) = 4096
Percent. of lock lists per application (MAXLOCKS) = 40
Lock timeout (sec) (LOCKTIMEOUT) = 240

/usr/DB/db2inst1/diag/db2inst1.nfy