DB2 FOR LUW / DB2FORLUW / 980 - DB2

HADR standby can shut down reporting "Invalid format in Extent 
header" when the following conditions are met: 
  * The primary and standby share an archive log path 
  * The standby is using a mirror log path 
  * The standby is going through local or remote catchup 
 
Our issue is that the active log path receives updates from the 
archive log path and the HADR primary.  The mirror log path only 
receives updates from the HADR primary.  This can cause 
information in the log headers to diverge during local/remote 
catchup.  This causes log header inconsistencies which results 
in the HADR standby being shutdown.

**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR users with a mirror log path                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* HADR standby can shut down reporting "Invalid format         * 
* inExtentheader" when the following conditions are met:* The  * 
* primary and standby share an archive log path* The standby   * 
* is using a mirror log path* The standby is going through     * 
* local or remote catchupOur issue is that the active log path * 
* receives updates fromthearchive log path and the HADR        * 
* primary.  The mirror log pathonlyreceives updates from the   * 
* HADR primary.  This can causeinformation in the log headers  * 
* to diverge duringlocal/remotecatchup.  This causes log       * 
* header inconsistencies whichresultsin the HADR standby being * 
* shutdown.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Remove the logs from the mirror log path on the standby      * 
* andre-activate.  First fixed in DB2 v9.8 fix pack 3.         * 
****************************************************************

Remove the logs from the mirror log path on the standby and 
re-activate.

DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.8 Fix Pack 4 for AIX and Linux
 DB2 Version 9.8 Fix Pack 5 for AIX and Linux
 

Remove the logs from the mirror log path on the standby and 
re-activate.  First fixed in DB2 v9.8 fix pack 3.

Remove the logs from the mirror log path on the standby and 
re-activate.

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

12.03.2010
17.01.2011
17.01.2011

9.8.FP3