Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC62417 Status: Closed

WHEN HADR PRIMARY IS IN 'WRITE SUSPEND' STATE, ISSUING AN HADR
TAKEOVER WILL MAKE BOTH PRIMARY AND STANDBY INACCESSIBLE.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
With an HADR pair set up (Machine A as HADR Primary, and Machine 
B as HADR Standby), the following introduces an error: 
1) Machine A: connect to db <dbname> 
2) Machine A: db2 set write suspend for db 
3) Machine B: takeover hadr for db <dbname> 
 
On Machine B, the 'takeover hadr' command will hang. 
 
On Machine A, the database connection is lost, and the following 
error may be encountered: 
 SQL1224N  The database manager is not able to accept new 
requests, has 
 terminated all requests in progress, or has terminated your 
particular request 
 due to an error or a force interrupt.  SQLSTATE=55032 
 
Further attempts to connect to the db on Machine A will yield: 
 SQL1776N  The command cannot be issued on an HADR standby 
database. Reason 
 code = "2". 
 
 
 
This problem can be avoided by unsetting 'write suspend' on 
Machine A, or by using the 'BY FORCE' option with the HADR 
takeover command.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all environment                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When primary is suspended during a takeover, the takeover    * 
* will hang.                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 v95 fp6                                       * 
****************************************************************
Local Fix:
This problem can be recovered from by issuing 'db2_kill' on 
Machine A, and then restarting.
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
we fix the problem in db2_v95fp6. After the fix, takeover on 
standby will return SQL1770N  Takeover HADR cannot complete. 
Reason code = "6". and suggestive message is in db2diag.log.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67827 IC67828 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.08.2009
13.05.2010
13.05.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)