DB2 - Problembeschreibung
Problem IC62417 | Status: Geschlossen |
WHEN HADR PRIMARY IS IN 'WRITE SUSPEND' STATE, ISSUING AN HADR TAKEOVER WILL MAKE BOTH PRIMARY AND STANDBY INACCESSIBLE. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
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 | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC67827 IC67828 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 06.08.2009 13.05.2010 13.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6 | |
Problem behoben lt. FixList in der Version |