Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC67827 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 / 970 - 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 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.
verfügbare FixPacks:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
A graceful takeover command (issued on the HADR Standby) will 
fail if the corresponding HADR Primary is in 'write suspend' 
state.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.04.2010
30.09.2010
30.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList