I'm using DB2 V9.1. I got this on HADR server (secondary) this morning. Just wondering if there's something that I should do to prevent these kind of problems. Not sure how this happened.


2010-04-12-06.46.11.028659-300 I1119A453 LEVEL: Warning
PID : 1614000 TID : 1 PROC : db2logts (PSFTPROD) 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, recovery manager, sqlpWriteDirtyList, probe:55 DATA #1 : <preformatted> Rollforward does not have log skipping information for log file 16513.Therefore, during tablespace rollforward, this log file will be replayed unconditionally. ExtentEntry 165

2010-04-12-06.46.11.036988-300 I1573A162 LEVEL: Warning
PID:1614000 TID:1 NODE:000 Title: SQLP_DBCB Dump File:/home/db2inst1/sqllib/db2dump/16140001.000


Attached is the 16140001.000 hexidecimal file. Has anyone ever encounter this issue before?

Thank you.

CC

whats your DIAGLEVEL ? Is it 4 ?

As per this APAR, this should be fixed in 8.2 FP 9, FP10 and FP10a which means you should see this as an informational message and can only be seen if the DIAGLEVEL is set to 4. But looks like you are getting it as a warning message eventhough you are in V9.1.

IBM IZ06273: MOVE LOG SKIPPING INFORMATION IN DB2DIAG.LOG FROM DIAGLEVEL 3 TO 4 - United States

I'm on diaglevel 3. I'm using DB2v9.1 FixPack 4.
Hmmm...

prodhadr$ db2 get dbm cfg | grep -i diaglevel
Diagnostic error capture level (DIAGLEVEL) = 3

CC

As it is clearly mentioned that the error can be ignored, you don't have to worry about that message. You might want to open a PMR to let them know that this is coming out as a warning message in 9.1 FP3