Troubleshooting
Problem
A Tivoli Storage Manager server is not usable during DB2 crash recovery. This technote provide a way to monitor the crash recovery progress.
Symptom
The Tivoli Storage Manager server instance startup hangs. Also, the "db2 connect to tsmdb1" command hangs.
Cause
The DB2 instance may experience a crash recovery under certain conditions. For example when DB2 was force terminated via command "db2_kill" or "kill -9". This crash recovery is a lengthy process which can take hours to complete.
Diagnosing The Problem
Review db2diag.log for crash recovery messages. For example :
2013-04-17-09.36.29.368832-300 I13647A510 LEVEL: Warning
PID : 50790862 TID : 3600 PROC : db2sysc 0
INSTANCE: tsminst1 NODE : 000 DB : TSMDB1
APPHDL : 0-7 APPID: *LOCAL.tsminst1.130417140404
AUTHID : TSMINST1
EDUID : 3600 EDUNAME: db2agent (TSMDB1) 0
MESSAGE : DIA2051W Forward phase of crash recovery has completed. Next
LSN is "0000259AD0276FD8".
The above message indicates that DB2 is experiencing the crash recovery.
Resolving The Problem
Login as the instance owner and execute the "db2 list utilities show detail" command. For example ::
$ db2 list utilities show detail
ID = 1
Type = CRASH RECOVERY
Database Name = TSMDB1
Partition Number = 0
Description = Crash Recovery
Start Time = 04/17/2013 09:04:15.432093
State = Executing
Invocation Type = User
Progress Monitoring:
Estimated Percentage Complete = 100
Phase Number = 1
Description = Forward
Total Work = 25811048626 bytes
Completed Work = 25811048626 bytes
Start Time = 04/17/2013 09:04:15.432099
Phase Number [Current] = 2
Description = Backward
Total Work = 25937697602 bytes
Completed Work = 25769328527 bytes
Start Time = 04/17/2013 09:36:29.368810
The crash recovery contains two phases. The above output shows the crash recovery is at phase 2 ( Phase Number [Current] = 2 ) and has completed "25769328527 bytes" out of a total of "25937697602 bytes".
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21634679