DB2 FOR LUW / DB2FORLUW / 950 - DB2

In a HADR primary failure scenario, the integrated HA solution 
may perform failover so the standby database will become 
primary. When the old primary is back online and available, the 
solution will automatically start the old primary as the new 
standby, this is called reintegration. Sometimes reintegration 
is not possible if there are new connections keeping the old 
primary database active. In these cases, db2_kill will be issued 
internally such that the next start up of the old primary 
instance will perform the reintegration successfully. 
 
 
This db2_kill is working as designed, but may not be desirable 
in some scenarios. This APAR will improve the reintegration code 
such that it minimize the chance of db2_kill happening.

**************************************************************** 
* USERS AFFECTED:                                              * 
* purescale users                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In a HADR primary failure scenario, the integrated HA        * 
* solution                                                     * 
* may perform failover so the standby database will become     * 
* primary. When the old primary is back online and available,  * 
* the                                                          * 
* solution will automatically start the old primary as the new * 
* standby, this is called reintegration. Sometimes             * 
* reintegration                                                * 
* is not possible if there are new connections keeping the old * 
* primary database active. In these cases, db2_kill will be    * 
* issued                                                       * 
* internally such that the next start up of the old primary    * 
* instance will perform the reintegration successfully.        * 
*                                                              * 
*                                                              * 
* This db2_kill is working as designed, but may not be         * 
* desirable                                                    * 
* in some scenarios. This APAR will improve the reintegration  * 
* code                                                         * 
* such that it minimize the chance of db2_kill happening.      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* will be  fixed   in  galileo                                 * 
****************************************************************

DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC77699 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

14.06.2011
24.05.2012
24.05.2012