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

IN AN AUTOMATED HADR ENVIRONMENT, FOLLOWING A REBOOT OF THE STAN DBY
SERVER, THE DATABASE MAY NOT BE REINTEGRATED AS THE STANDBY

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In an automated HADR environment, whereby a virtual IP address 
is not used for database client connections, it is possible for 
the HADR database to be mistakenly queried as activated at 
instance startup time and as a result the database is not 
activated. 
 
This is a result of database client connections attempting to 
connect to the standby database. If a Virtual IP address is used 
by database client connections, then this issue is avoidable. 
 
If this issue is reproduced, then the following syslog message 
will be seen on the standby at instance startup time: 
 
 Mar  3 16:23:23 host01 user:info db2V105_start.ksh[11206778]: 
deact ==        0
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR/TSA users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 FP7                                     * 
****************************************************************
Local-Fix:
Manually activate the HADR database on the standby server.
Lösung
Fixed in DB2 V10.5 FP7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.04.2015
20.01.2016
20.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList