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 IC70395 Status: Geschlossen

IN DB2 V9.5, IN A DB2HAICU HADR ENVIRONMENT, AFTER A FAILOVER, HADR
RESOURCE MAY PREVENT THE RESTORE ON THE STANDBY

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
In an HADR environment, after a failover, if the old primary 
database was dropped, the hadrV95_monitor.ksh script could 
prevent the restore of a new database by issuing a FORCE 
APPLICATION against the restore process. 
 
The force could occur because the 'reintegrate in progress' flag 
is still set.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of HA monitoring scripts                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See above.                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Fix Pack 7 or later.                              * 
****************************************************************
Local-Fix:
In the hadrV95_monitor.ksh script, there is a loop that lists 
 
applications for the database and forces them.  The loop control 
line should include "show detail" on the snapshot and a grep -v 
"Restoring" to skip agents performing the restore. 
 
The modified line should resemble: 
   su - ${candidate_P_instance?} -c "export LANG=C;db2 list 
applications for database ${DB2HADRDBNAME?} show detail | grep 
-v "Restoring" | awk '{print \$3}' | grep ^"[0-9]" | while 
read applid; do
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.5 Fix Pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC71076 IC71111 IC71174 IC71208 IC71252 IC71274 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.08.2010
15.11.2010
15.11.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP7
Problem behoben lt. FixList in der Version
9.1.0.7 FixList
9.5.0.7 FixList