Skip to Content
0
Former Member
Jul 03, 2014 at 02:37 AM

Corrupt files in log_dir

140 Views

Dear All,

In our development database, a logfile under log_dir got corrupted. The timestamp on the logfile is set at 20th may, when the system was last stopped.

Now the system is unable to perform crash recovery, because of the corrupt log file.

Is there any way to start the development database bypassing the files in log_dir?

Given below are the logs from db2diag.log:

2014-07-02-12.06.46.953000+480 E245790493F478 LEVEL: Warning

PID : 3172 TID : 2200 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 2200 EDUNAME: db2agent (BPD) 0

FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410

MESSAGE : ADM1530E Crash recovery has been initiated.

2014-07-02-12.06.46.968000+480 I245790973F522 LEVEL: Warning

PID : 3172 TID : 2200 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 2200 EDUNAME: db2agent (BPD) 0

FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000

DATA #1 : <preformatted>

Using parallel recovery with 4 agents 34 QSets 102 queues and 64 chunks

2014-07-02-12.07.04.484000+480 I245791497F412 LEVEL: Error

PID : 3172 TID : 3288 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000

EDUID : 3288 EDUNAME: db2lfr (BPD) 0

FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog, probe:5300

MESSAGE : ZRC=0x860F0002=-2045837310=SQLO_DCRC "CRC error (DD)"

DIA8401C A CRC error has occurred.

2014-07-02-12.07.04.546000+480 I245791911F415 LEVEL: Error

PID : 3172 TID : 3288 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000

EDUID : 3288 EDUNAME: db2lfr (BPD) 0

FUNCTION: DB2 UDB, recovery manager, sqlplfrIsLogFromValidChain, probe:5174

DATA #1 : <preformatted>

Problem with log file S0015634.LOG, PId 1400214503, lfrPrevExtCId 1400236864

2014-07-02-12.07.04.546000+480 I245792328F366 LEVEL: Error

PID : 3172 TID : 3288 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000

EDUID : 3288 EDUNAME: db2lfr (BPD) 0

FUNCTION: DB2 UDB, recovery manager, sqlplfrIsLogFromValidChain, probe:5175

MESSAGE : Ignore log file problem for crash recovery.

2014-07-02-12.07.04.546000+480 I245792696F454 LEVEL: Warning

PID : 3172 TID : 3288 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000

EDUID : 3288 EDUNAME: db2lfr (BPD) 0

FUNCTION: DB2 UDB, data protection services, sqlpgarl, probe:99

MESSAGE : INFO ONLY: Found an old page in the log file: ByteOffset 4076,

PageLso 1089239038220 highLso 1089280189517 lowLso 1089280185441

2014-07-02-12.07.04.562000+480 I245793152F539 LEVEL: Error

PID : 3172 TID : 3292 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 3292 EDUNAME: db2redom (BPD) 0

FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:1275

RETCODE : ZRC=0x860F0002=-2045837310=SQLO_DCRC "CRC error (DD)"

DIA8401C A CRC error has occurred.

2014-07-02-12.07.04.578000+480 I245793693F539 LEVEL: Error

PID : 3172 TID : 3292 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 3292 EDUNAME: db2redom (BPD) 0

FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:1180

RETCODE : ZRC=0x860F0002=-2045837310=SQLO_DCRC "CRC error (DD)"

DIA8401C A CRC error has occurred.

2014-07-02-12.07.04.781000+480 I245794234F593 LEVEL: Error

PID : 3172 TID : 2200 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 2200 EDUNAME: db2agent (BPD) 0

FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:640

DATA #1 : String, 142 bytes

Crash recovery failed with rc -2045837310

LowtranLSN 000000FED9C91DAE MinbuffLSN 000000FED0852B0A

Recovery started on log file S0015631.LOG.

2014-07-02-12.07.04.781000+480 I245794829F545 LEVEL: Severe

PID : 3172 TID : 2200 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 2200 EDUNAME: db2agent (BPD) 0

FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::RecoverDatabase, probe:16

DATA #1 : Hexdump, 4 bytes

0x000000000E4D85F4 : 0200 0F86 ....

2014-07-02-12.07.04.781000+480 I245795376F544 LEVEL: Error

PID : 3172 TID : 2200 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 2200 EDUNAME: db2agent (BPD) 0

FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::RecoverDatabase, probe:16

DATA #2 : Hexdump, 4 bytes

0x000000000E4D85F4 : 0200 0F86 ....

2014-07-02-12.07.04.781000+480 E245795922F515 LEVEL: Error

PID : 3172 TID : 2200 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 2200 EDUNAME: db2agent (BPD) 0

FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::RecoverDatabase, probe:60

MESSAGE : ADM1532E Crash recovery has failed with SQLCODE "-1042".

2014-07-02-12.07.04.781000+480 E245796439F991 LEVEL: Critical

PID : 3172 TID : 2200 PROC : db2syscs.exe

INSTANCE: DB2BPD NODE : 000 DB : BPD

APPHDL : 0-11 APPID: fe80::551c:a581:a78b:1185%10.49543.140702040644

AUTHID : SAPBPD

EDUID : 2200 EDUNAME: db2agent (BPD) 0

FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::MarkDBBad, probe:10

MESSAGE : ADM14001C An unexpected and critical error has occurred:

"DBMarkedBad". The instance may have been shutdown as a result.

"Automatic" FODC (First Occurrence Data Capture) has been invoked and

diagnostic information has been recorded in directory

"\\BPCDEV\db2dumpBPD\FODC_DBMarkedBad_2014-07-02-12.07.04.781001_0000

\". Please look in this directory for detailed evidence about what

happened and contact IBM support if necessary to diagnose the

problem.