|
Problem IC66120
|
Status: Closed |
Invalid format in Extent header brings down HADR standby |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| available fix packs: |
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
|
| Solution |
Upgrade to DB2 v9.7 FP2 or newer |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67196 IZ75533
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.02.2010
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
