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 IC67393 Status: Closed

STANDBY WOULD NOT REINTEGRATED INTO THE HADR PAIR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After primary server is rebooted the other database server 
takeover,  once the rebooted server up, both hadr databases on 
each server stated themselves as primary database. 
 
When they rebooted the primary server, TSA did failover and 
brought up standby as primary. When primary came up, it started 
database as 
PRMIARY again.  It is a split brain situation. primary on both 
the servers. 
 
The problem is standby would not reintegrated into the HADR 
pair. 
 
The customer is using csh on their environment.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Environment where default shell is csh                       * 
* Applies to integrated HA, HADR scenario only.                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After primary server is rebooted the other database server   * 
*                                                              * 
* takeover,  once the rebooted server up, both hadr databases  * 
* on                                                           * 
* each server stated themselves as primary database.           * 
*                                                              * 
*                                                              * 
*                                                              * 
* When they rebooted the primary server, TSA did failover and  * 
*                                                              * 
* brought up standby as primary. When primary came up, it      * 
* started                                                      * 
* database as                                                  * 
*                                                              * 
* PRMIARY again.  It is a split brain situation. primary on    * 
* both                                                         * 
* the servers.                                                 * 
*                                                              * 
*                                                              * 
*                                                              * 
* The problem is standby would not reintegrated into the HADR  * 
*                                                              * 
* pair.                                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7.0.2                                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Upgrade to DB2 v9.7.0.2
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67406 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.03.2010
08.11.2012
08.11.2012
Problem solved at the following versions (IBM BugInfos)
9.7.0.2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList