DB2 FOR LUW / DB2FORLUW / A10 - DB2

Crash recovery may fail with SQL1036 if the mirror log is more 
recent than the same active log due to lost 
I/O on the active file. 
. 
You will encounter the following error in the db2diag.log: 
. 
2011-06-21-12.03.38.277038+000 I36717E526          LEVEL: 
Warning 
PID     : 14200                TID  : 46912933718336PROC : 
db2sysc 
INSTANCE: db2inst1                   NODE : 000          DB   : 
SAMPLE 
EDUID   : 19                   EDUNAME: db2loggr (SAMPLE) 
FUNCTION: DB2 UDB, data protection services, sqlpgole, 
probe:1200 
DATA #1 : <preformatted> 
Primary and mirror logpath log file headers are not consistent. 
Primary log file: '/activelog/S0000021.LOG' 
Mirror log file: '/mirrorlog/S0000021.LOG' 
. 
 
 
2011-06-17-15.22.05.323252+000 E378877E832  Error (OS) 
PID     : 14179                TID  : 46912933718336PROC : 
db2sysc 
INSTANCE: db2inst1                   NODE : 000          DB   : 
SAMPLE 
EDUID   : 19                   EDUNAME: db2loggr (SAMPLE) 
FUNCTION: DB2 UDB, oper system services, sqloseek, probe:100 
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
CALLED  : OS, -, lseek                            OSERR: EBADF 
(9) 
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
0x00002AAAC4BFCC70 : FFFF FFFF 0000 0000 
........ 
DATA #2 : File Offset, 8 bytes 
0 
DATA #3 : unsigned integer, 8 bytes 
2 
DATA #4 : String, 105 bytes 
Search for ossError*Analysis probe point after this log entry 
for further 
self-diagnosis of this problem. 
 
. 
The issue is that db2 must use the mirror log file (because the 
active log has less data due to a lost I/O), 
but then db2 uses the filehandle for the active log when 
checking the file size.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using Mirror log path                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Make a backup of the log file in the active log path, and    * 
* delete itt from the active log path.                         * 
****************************************************************

Make a backup of the log file in the active log path, and delete 
it from the active log path.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem First Fixed in DB2 Version 10.1 Fix Pack 1

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

12.06.2012
07.12.2012
07.12.2012