By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,334 Members | 1,861 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,334 IT Pros & Developers. It's quick & easy.

Crash recovery

P: n/a
Hi All :
I use db2 8.1 fixpack 3 on AIX.
I recieved the following message in the diaglog
================================================== ====
ADM7513W Database manager has started.

2007-01-13-18.55.08.262174 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
base sys utilities sqledint Probe:30

Crash Recovery is needed.

2007-01-13-18.55.09.139720 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
recovery manager sqlpresr Probe:410 Database:MUMAR

Crash recovery started. LowtranLSN 00000005D26EBE0C MinbuffLSN
00000005D26B120C

2007-01-13-18.55.09.270600 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
recovery manager sqlprecm Probe:125 Database:MUMAR

Using parallel recovery with 3 agents 5 QSets 35 queues and 16 chunks
2007-01-13-18.55.10.121525 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
recovery manager sqlprecm Probe:400 Database:MUMAR

DIA2051W Forward phase of crash recovery has completed. Next LSN is
"00000005D279C7A2".

2007-01-13-18.55.10.415121 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
recovery manager sqlpresr Probe:3170 Database:MUMAR

Crash recovery completed. Next LSN is 00000005D279C7A2
================================================== =============
Can anyone help me out with this and suggest ways to avoid it in future.

Jan 15 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
"Racerx" <p.**********@gmail.comwrote in message
news:11**********************@51g2000cwl.googlegro ups.com...
Hi All :
I use db2 8.1 fixpack 3 on AIX.
I recieved the following message in the diaglog
================================================== ====
ADM7513W Database manager has started.

2007-01-13-18.55.08.262174 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
base sys utilities sqledint Probe:30

Crash Recovery is needed.

2007-01-13-18.55.09.139720 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
recovery manager sqlpresr Probe:410 Database:MUMAR

Crash recovery started. LowtranLSN 00000005D26EBE0C MinbuffLSN
00000005D26B120C

2007-01-13-18.55.09.270600 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
recovery manager sqlprecm Probe:125 Database:MUMAR

Using parallel recovery with 3 agents 5 QSets 35 queues and 16 chunks
2007-01-13-18.55.10.121525 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
recovery manager sqlprecm Probe:400 Database:MUMAR

DIA2051W Forward phase of crash recovery has completed. Next LSN is
"00000005D279C7A2".

2007-01-13-18.55.10.415121 Instance:db2inst1 Node:000
PID:467078(db2agent (mumar) 0) TID:1
Appid:GA010302.O03F.01101B9A3444
recovery manager sqlpresr Probe:3170 Database:MUMAR

Crash recovery completed. Next LSN is 00000005D279C7A2
================================================== =============
Can anyone help me out with this and suggest ways to avoid it in future.
That means the instance crashed or was manually stopped while transactions
were in progress. Upon restart, DB2 backs out the uncommitted changes to the
databases.
Jan 15 '07 #2

P: n/a
Crash recovery completed. Next LSN is 00000005D279C7A2
================================================== =============
Can anyone help me out with this and suggest ways to avoid it in future.
Your system crashed. Did you have any power outage ?

If not, you will have to check the log before these lines and check why
it happened. It is always a good idea to contact IBM support upon
instance crashes.

-M

Jan 15 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.