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

Database Marked Bad

P: n/a
Hello,

In an attempt to save disk space, I went in and gzipped all of the log
files for my database running DB2 version 7.2 . This resulted in the
database being marked bad because a log file was no longer found (I
think).

Here is an excerpt from db2diag.log:

String Title:sqleMarkDBad: PID:7980 Node:000
Marking the database bad.

2007-05-10-05.44.26.211513 Instance:db2inst1 Node:000
PID:7980(db2agent (V1DB)) Appid:C0A80A21.95D2.070510124202
relation_data_serv sqlrr_signal_handler Probe:10 Database:V1DB
DIA7107I Execution of a component signal handling function has begun.
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:APM COMMON INFO
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:PACKAGE ENTRY
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:USED_IN_UOW BIT
VECTOR
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:Recursive
dump_sect
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:SECTION NUMBER
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:SECTION DIR
ENTRY
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:cache cb

I have a backup that is pretty old and all of the log files so I can
rollforward, but was wondering if there is a way since I actually HAVE
the ability to recover -- it just may take me a while.

Is there a way that I can use the dump files that are mentioned in the
line after the "marking the database bad" error message in order to
make my log file useable again? Every time I attempt to connect to
the database, I get a generic system error:
SQL1042C An unexpected system error occurred. SQLSTATE=58004

It apparently tries to do a crash recovery but fails:
007-05-10-11.37.19.131481 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
base_sys_utilities sqledint Probe:0 Database:V1DB

Crash Recovery is needed.

2007-05-10-11.37.19.195627 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:1 Database:V1DB
DIA3908W Crash recovery has been initiated. Lowtran LSN is
"00054BB9D2A3",
Minbuff LSN is "00054BB9D2A3".

2007-05-10-11.37.19.200298 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlprecm Probe:125 Database:V1DB

Using parallel recovery with 3 agents 3 QSets 21 queues and 2 chunks

2007-05-10-11.37.19.225329 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
data_protection sqlpgrlg Probe:170 Database:V1DB

ThisLsn: 0005 4bb9 d2a3 ..K...

Dump File:/home/db2inst1/sqllib/db2dump/29404.000 Data:SQLP_DBCB

2007-05-10-11.37.19.232828 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
data_protection sqlpgrlg Probe:0 Database:V1DB

Error -6899 when reading LSN 0005 4BB9 D2A3 from log file S0001187.LOG

2007-05-10-11.37.19.237101 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpPRecReadLog Probe:50 Database:V1DB
DIA3714C Logging can not continue due to an error.

ZRC=0xFFFFE50D

2007-05-10-11.37.19.315427 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:10 Database:V1DB
DIA3910W Crash recovery completed. Return Code = "-6899"

2007-05-10-11.37.19.316331 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:10 Database:V1DB

ThisLsn: 0005 4bb9 d2a3 ..K...

Dump File:/home/db2inst1/sqllib/db2dump/29404.000 Data:SQLP_DBCB

2007-05-10-11.37.19.232828 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
data_protection sqlpgrlg Probe:0 Database:V1DB

Error -6899 when reading LSN 0005 4BB9 D2A3 from log file S0001187.LOG

2007-05-10-11.37.19.237101 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpPRecReadLog Probe:50 Database:V1DB
DIA3714C Logging can not continue due to an error.

ZRC=0xFFFFE50D

2007-05-10-11.37.19.315427 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:10 Database:V1DB
DIA3910W Crash recovery completed. Return Code = "-6899"

2007-05-10-11.37.19.316331 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:10 Database:V1DB

Recovery started on log file: 5330 3030 3131 3837 2e4c
4f47 S0001187.LOG
2007-05-10-11.37.19.320371 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
base_sys_utilities sqlesrsu Probe:16 Database:V1DB

DiagData
0de5 ffff ....
2007-05-10-11.37.19.324473 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
base_sys_utilities sqlesrsu Probe:16 Database:V1DB

RIDS/sqlesrsu MS/UNK_REC_ERR PRCS/160de5
ffff ....
2007-05-10-11.37.19.328607 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
base_sys_utilities sqlesrsu Probe:110 Database:V1DB

Restart failed with sqlcode: eefb ffff
If there is a way to fix the current database, using some of these
dump files, that'd be wonderful. Thanks for any suggestions anyone
has.

Sincerely,

Scott

May 10 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Scott Jones wrote:
Hello,

In an attempt to save disk space, I went in and gzipped all of the log
files for my database running DB2 version 7.2 . This resulted in the
database being marked bad because a log file was no longer found (I
think).
What happens if you stop the database, unzip the logfiles and start the
db again?

/Lennart

>
Here is an excerpt from db2diag.log:

String Title:sqleMarkDBad: PID:7980 Node:000
Marking the database bad.

2007-05-10-05.44.26.211513 Instance:db2inst1 Node:000
PID:7980(db2agent (V1DB)) Appid:C0A80A21.95D2.070510124202
relation_data_serv sqlrr_signal_handler Probe:10 Database:V1DB
DIA7107I Execution of a component signal handling function has begun.
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:APM COMMON INFO
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:PACKAGE ENTRY
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:USED_IN_UOW BIT
VECTOR
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:Recursive
dump_sect
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:SECTION NUMBER
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:SECTION DIR
ENTRY
Dump File:/home/db2inst1/sqllib/db2dump/7980.000 Data:cache cb

I have a backup that is pretty old and all of the log files so I can
rollforward, but was wondering if there is a way since I actually HAVE
the ability to recover -- it just may take me a while.

Is there a way that I can use the dump files that are mentioned in the
line after the "marking the database bad" error message in order to
make my log file useable again? Every time I attempt to connect to
the database, I get a generic system error:
SQL1042C An unexpected system error occurred. SQLSTATE=58004

It apparently tries to do a crash recovery but fails:
007-05-10-11.37.19.131481 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
base_sys_utilities sqledint Probe:0 Database:V1DB

Crash Recovery is needed.

2007-05-10-11.37.19.195627 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:1 Database:V1DB
DIA3908W Crash recovery has been initiated. Lowtran LSN is
"00054BB9D2A3",
Minbuff LSN is "00054BB9D2A3".

2007-05-10-11.37.19.200298 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlprecm Probe:125 Database:V1DB

Using parallel recovery with 3 agents 3 QSets 21 queues and 2 chunks

2007-05-10-11.37.19.225329 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
data_protection sqlpgrlg Probe:170 Database:V1DB

ThisLsn: 0005 4bb9 d2a3 ..K...

Dump File:/home/db2inst1/sqllib/db2dump/29404.000 Data:SQLP_DBCB

2007-05-10-11.37.19.232828 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
data_protection sqlpgrlg Probe:0 Database:V1DB

Error -6899 when reading LSN 0005 4BB9 D2A3 from log file S0001187.LOG

2007-05-10-11.37.19.237101 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpPRecReadLog Probe:50 Database:V1DB
DIA3714C Logging can not continue due to an error.

ZRC=0xFFFFE50D

2007-05-10-11.37.19.315427 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:10 Database:V1DB
DIA3910W Crash recovery completed. Return Code = "-6899"

2007-05-10-11.37.19.316331 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:10 Database:V1DB

ThisLsn: 0005 4bb9 d2a3 ..K...

Dump File:/home/db2inst1/sqllib/db2dump/29404.000 Data:SQLP_DBCB

2007-05-10-11.37.19.232828 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
data_protection sqlpgrlg Probe:0 Database:V1DB

Error -6899 when reading LSN 0005 4BB9 D2A3 from log file S0001187.LOG

2007-05-10-11.37.19.237101 Instance:db2inst1 Node:000
PID:29404(db2agnsc (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpPRecReadLog Probe:50 Database:V1DB
DIA3714C Logging can not continue due to an error.

ZRC=0xFFFFE50D

2007-05-10-11.37.19.315427 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:10 Database:V1DB
DIA3910W Crash recovery completed. Return Code = "-6899"

2007-05-10-11.37.19.316331 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
recovery_manager sqlpresr Probe:10 Database:V1DB

Recovery started on log file: 5330 3030 3131 3837 2e4c
4f47 S0001187.LOG
2007-05-10-11.37.19.320371 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
base_sys_utilities sqlesrsu Probe:16 Database:V1DB

DiagData
0de5 ffff ....
2007-05-10-11.37.19.324473 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
base_sys_utilities sqlesrsu Probe:16 Database:V1DB

RIDS/sqlesrsu MS/UNK_REC_ERR PRCS/160de5
ffff ....
2007-05-10-11.37.19.328607 Instance:db2inst1 Node:000
PID:17871(db2agent (V1DB)) Appid:C0A80A32.EB88.070510152851
base_sys_utilities sqlesrsu Probe:110 Database:V1DB

Restart failed with sqlcode: eefb ffff
If there is a way to fix the current database, using some of these
dump files, that'd be wonderful. Thanks for any suggestions anyone
has.

Sincerely,

Scott
May 11 '07 #2

P: n/a


If you have a backup copy of your database before the problem, you
may restore the backup copy..
If you dont, check with system restore(in case of windows..) you can
take backup copy and restore it !

@Ekta.

May 14 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.