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

IN A HADR HA(TSA) ENVIRONMENT, IN THE EVENT OF A PRIMARY SERVER FAILURE,
THE STANDBY MAY NOT BE REINTEGRATED ON INSTANCE STARTUP

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In the event of a primary server failure, the IBM.Test 
Reintegration flag is being created after the db2V105_start.ksh 
script is run causing the script to try to activate the database 
instead of reintegrating it as a standby. 
 
In this case, the following syslog messages are seen on the old 
primary as it is starting up DB2: 
 
Mar 13 15:42:55 host4 db2V105_start.ksh[2769]: Entered 
/usr/sbin/rsct/sapolicies/db2/db2V105_start.ksh, db2inst1, 0 
Mar 13 15:42:55 host4 db2V105_start.ksh[2769]: Able to cd to 
/home/db2inst1/sqllib : 
/usr/sbin/rsct/sapolicies/db2/db2V105_start.ksh, db2inst1, 0 
Mar 13 15:42:56 host4 db2V105_start.ksh[2769]: 1 partitions 
total: /usr/sbin/rsct/sapolicies/db2/db2V105_start.ksh, 
db2inst1, 0 
Mar 13 15:43:08 host4 db2V105_start.ksh[2769]: deact == 1 
Mar 13 15:43:08 host4 db2V105_start.ksh[2769]: su - db2inst1 -c 
db2 activate database HADRDB 
 
The expected behavior is for the db2V105_start.ksh script to 
start the HADR database as the standby instead of activating it.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 7                   * 
****************************************************************
Local-Fix:
N/A
Lösung
Problem was first fixed in DB2 Version 10.5 and Fix Pack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.03.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