Symptom
DB2 does not restart after a snapshot recovery and the following error is observed in Db2diag.log:
LEVEL: Error
PID : 12345678 TID : 00000 PROC : db2sysc 0
INSTANCE: db2sid NODE : 000 DB : SID
APPHDL : 0-00 APPID:
AUTHID : SAPSID
EDUID : 11111 EDUNAME: db2agent (SID) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbStartPools, probe:22
MESSAGE : ZRC=0x800200F3=-2147352333=SQLB_FAIL2_SUSPEND_WRITE_ON
"Restart failed"
LEVEL: Severe
PID : 12345678 TID : 00000 PROC : db2sysc 0
INSTANCE: db2sid NODE : 000 DB : SID
APPHDL : 0-00 APPID:
AUTHID : SAPSID
EDUID : 11111 EDUNAME: db2agent (SID) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbStartPools, probe:22
MESSAGE : ADM6024C The database cannot be restarted because table
spaces
cannot be brought ONLINE as a result of an outstanding WRITE SUSPEND.
To restart the database specify WRITE RESUME on the RESTART DATABASE
command.
Read more...
Environment
DB2 for LUW database releases:
- V9.7
- 10.1
- 10.5
Product
Keywords
db2inidb, split mirror, source, suspend, resume, clone, relocate, , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.