DB2 FOR LUW / DB2FORLUW / 970 - DB2

WHEN LOG MIRRORING IS ACTIVE THE LOG MANAGER EDU CAN INCORRECTLY 
ASSUME A LOG FILE 
HAS BEEN ARCHIVED 
 
Before the problem is encountered, the following message is 
observed in the db2diag.log 
 
2010-09-20-02.55.18.298321+120 E36642852A764      LEVEL: Warning 
PID     : 21711                TID  : 1           PROC : 
db2loggw (sample) 0 
INSTANCE: db2inst1             NODE : 000 
FUNCTION: DB2 UDB, data protection services, sqlpgStartMfhEntry, 
probe:7520 
MESSAGE : ADM1839W  An error occurred while DB2 was writing log 
data to log 
          file "S0000053.LOG" on path 
"/db2/logs/log_dir2/NODE0000/".  The log 
          file is still available on log path 
"/db2/logs/log_dir1/NODE0000/". 
          DB2 will attempt to use both paths for subsequent log 
files.  In the 
          meantime, check that the specified log path in which 
the error 
          occurred exists and is accessible.  Also check that 
there is space 
          available in the file system. 
 
2010-09-20-02.28.38.973018+120 E36783848A406      LEVEL: Warning 
PID     : 21711                TID  : 1           PROC : 
db2loggw (sample) 0 
INSTANCE: db2inst1             NODE : 000 
FUNCTION: DB2 UDB, data protection services, 
sqlpgCompleteMfhEntry, probe:6080 
MESSAGE : ADM1840W  The error on log path 
"/db2/logs/log_dir1/NODE0000/" has 
          been resolved.  DB2 will now write log files to this 
path. 
 
 
This message typically occurs after a problem accessing either 
of the log mirroring paths. 
After resolving the problem and after a restart of the db2 
instance, DB2 will incorrectly 
reuse the affected log file(s). 
 
The following message can then be observed in the db2diag.log : 
 
2010-09-20-14.47.57.293042+120 I1570031A315       LEVEL: Warning 
 
PID     : 5403                 TID  : 1           PROC : 
 
db2logmgr (SAMPLE) 0 
 
INSTANCE: db2inst               NODE : 000 
 
FUNCTION: DB2 UDB, data protection services, 
 
sqlpgArchiveLogFile, probe:2100 
 
MESSAGE : Unable to find a useable log on any log path. 
 
After this, rollforward recovery problems will occur if the 
affected log(s) would be needed for this.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* WHEN LOG MIRRORING IS ACTIVE THE LOG MANAGER EDU CAN         * 
* INCORRECTLY ASSUME A LOG FILE HAS BEEN ARCHIVED.             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7FP4                                   * 
****************************************************************

Workaround : 
To ensure recovery is still possible a new database backup 
should be taken 
where the affected log files would not be required.

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First Fixed in v9.7FP4 or higher

keiner bekannt / siehe Local-Fix

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

15.10.2010
13.06.2011
13.06.2011

9.7.FP4