Hmm, it looks like you have a 11GB recovery log. If it was 97-100 %
full at the time it crashed (or was halted), it is most likely replaying all
11GB of those transactions. I'm not sure how long it would take to run 11G
of db updates, but I'm thinking that 30 minutes to 1 hour would not be
unreasonable (it all depends on your disk access speed).
You should run some sort of monitor on your system (iostat or topas
or monitor) to make sure that the server is not hung, but is actually
processing all those transactions. You should be seeing lots of reads from
the recovery log disks, and probably almost just as many writes to the disks
with the DB volumes on them. Probably also some paging going on.
Cross your fingers....
Ben
-----Original Message-----
From: Hokanson, Mark [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 1:19 PM
To: [EMAIL PROTECTED]
Subject: HELP: MVS TSM Server Hanging on Boot
This morning we noticed our TSM recovery log was ~97-100% full.
The server was still up but we couldn't log in. We halted the server,
increased the recovery log, and are trying to bring the server back up.
The problem is the server is stuck in Recovery log undo pass in progress.
10.36.06 STC24351 ANR0900I Processing options file dsmserv.opt.
10.36.07 STC24351 ANR0990I Server restart-recovery in progress.
10.36.30 STC24351 ANR0200I Recovery log assigned capacity is 11780
megabytes.
10.36.30 STC24351 ANR0201I Database assigned capacity is 53728 megabytes.
10.36.30 STC24351 ANR0306I Recovery log volume mount in progress.
10.44.07 STC24351 ANR0353I Recovery log analysis pass in progress.
11.57.38 STC24351 ANR0354I Recovery log redo pass in progress.
12.52.38 STC24351 ANR0355I Recovery log undo pass in progress.
12.52.40 STC24351 ANR0362W Database usage exceeds 88 %% of its assigned
capacity
Can anyone please advise?
Mark Hokanson
Thomson Legal and Regulatory
