home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC73673 Status: Geschlossen

FAILED_OFFLINE STATE PERSISTS AFTER STANDBY DATABASE RETURNS TO PEER STATE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Currently in integrated HA with HADR setup, if the Primary 
machine is rebooted, the Standby will takeover to become new 
Primary as expected. When the old Primary machines comes back 
alive, it is expected to become the new Standby (reintegration) 
such that the hadr pair resume Peer state with no manual 
intervention. 
 
This does happen at the DB2 level (verified by db2pd -hadr). 
However, at the SA MP level, lssam will show the old Primary is 
 
still "FAILED OFFLINE" despite HADR db pair is already in Peer. 
This TSA resource state can be set only via running SA MP 
command 
"resetrsrc" manually or recreating the cluster. If the "FAILED 
OFFLINE" state is not reset and a second failure occur, the next 
failover attempt will fail. 
 
This APAR fix will eliminate the need to manually run the 
"resetrsrc" command after reintegration occurs.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HA/HADR integrated solution users                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply V97FP4                                                 * 
****************************************************************
Local-Fix:
Run reintegration, manually run the following SA MP command: 
resetrsrc -s "Name = '<hadr_resource_name>' AND NodeNameList = 
{'<current_standby_node>'}" IBM.Application
verfügbare FixPacks:
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
After applying the fix, the SA MP resource state will change 
from Failed Offline back to Offline automatically after 
successful reintegration of old Primary database.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.01.2011
28.04.2011
28.04.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList