DB2 - Problem description
Problem IC67827 | 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 / 970 - 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 users of HADR * **************************************************************** * PROBLEM DESCRIPTION: * * Old HADR Primary becomes inaccessible if a takeover * * occurswhile in 'write suspend' state . * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7 Fixpack 3 * **************************************************************** | |
Local Fix: | |
This problem can be recovered from by issuing 'db2_kill' on Machine A, and then restarting. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
A graceful takeover command (issued on the HADR Standby) will fail if the corresponding HADR Primary is in 'write suspend' state. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.04.2010 30.09.2010 30.09.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |