|
Problem IC64747
|
Status: Closed |
DB2 HADR STANDBY CAN LOOSE TRACK OF ARCHIVED LOGS AFTER TAKEOVER BY FORCE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Under the following circumstances DB2 HADR STANDBY can
loose track of archived logs after a TAKEOVER BY FORCE:
- serious (HW) problems with primary database server.
- takeover by force and the standby becomes the new primary.
- old primary is defect and cannot be used as standby
anymore.
- "stop hadr" command on new primary so it becomes a standard
server.
- ONLINE BACKUP with INCLUDE LOGS options
A backup with INCLUDE LOGS triggers LOG ARCHIVE, but DB2 starts
with S0000000.LOG, ie. the very old (first) log file ever,
which of course is not available anymore. |
| Problem Summary: |
USERS AFFECTED: All using HADR
PROBLEM DESCRIPTION:
see ERROR DESCRIPTION
PROBLEM SUMMARY:
see ERROR DESCRIPTION |
| Local Fix: |
n/a |
| 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 |
The complete fix for this problem first appears in DB2 UDB
Version 9.7 FixPak 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.11.2009
18.05.2010
18.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
