home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC70395 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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
available fix packs:
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

Solution
Problem was first fixed in Version 9.5 Fix Pack 7.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC71076 IC71111 IC71174 IC71208 IC71252 IC71274 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.08.2010
15.11.2010
15.11.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList