DB2 - Problem description
|Problem IC64739||Status: Closed|
DB2 HADR STANDBY CAN LOOSE TRACK OF ARCHIVED LOGS AFTER TAKEOVER BY FORCE
DB2 FOR LUW / DB2FORLUW / 910 - DB2
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.
USERS AFFECTED All using HADR PROBLEM DESCRIPTION see ERROR DESCRIPTION PROBLEM SUMMARY see ERROR DESCRIPTION
|available fix packs:|
The complete fix for this problem first appears in DB2 UDB Version 9.1 FixPak 9.
not known / see Local fix
Date - problem reported : Date - problem closed : Date - last modified :
23.11.2009 14.04.2010 14.04.2010
|Problem solved at the following versions (IBM BugInfos)|
|Problem solved according to the fixlist(s) of the following version(s)|