home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66120 Status: Geschlossen

Invalid format in Extent header brings down HADR standby

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of HADR with mirror log path shared between theprimary * 
* and standby                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* HADR standby can shut down reporting "Invalid format         * 
* inExtent 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 catchupOur issue is that the active log path * 
* receives updates fromthe archive log path and the HADR       * 
* primary.  The mirror logpath only receives updates from the  * 
* HADR primary.  This cancause information in the log headers  * 
* to diverge duringlocal/remote catchup.  This causes log      * 
* headerinconsistencies which results in the HADR standby      * 
* beingshutdown.                                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP2 or newer                             * 
****************************************************************
Local-Fix:
Remove the logs from the mirror log path on the standby and 
re-activate.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Upgrade to DB2 v9.7 FP2 or newer
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67196 IZ75533 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.02.2010
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList