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

UNEXPECTED DB2_KILL ISSUED BY TSA SCRIPTS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 users using TSA scripts                                  * 
**************************************************************** 
* 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:                                              * 
* First fixed in db2 v9.7 fixpack 5                            * 
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.07.2011
20.12.2011
20.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version