DB2 FOR LUW / DB2FORLUW / A10 - DB2

In the event of a primary server failure, the IBM.Test 
Reintegration flag is being created after the db2V10_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 db2V10_start.ksh[2769]: Entered 
/usr/sbin/rsct/sapolicies/db2/db2V10_start.ksh, db2inst1, 0 
Mar 13 15:42:55 host4 db2V10_start.ksh[2769]: Able to cd to 
/home/db2inst1/sqllib : 
/usr/sbin/rsct/sapolicies/db2/db2V10_start.ksh, db2inst1, 0 
Mar 13 15:42:56 host4 db2V10_start.ksh[2769]: 1 partitions 
total: /usr/sbin/rsct/sapolicies/db2/db2V10_start.ksh, 
db2inst1, 0 
Mar 13 15:43:08 host4 db2V10_start.ksh[2769]: deact == 1 
Mar 13 15:43:08 host4 db2V10_start.ksh[2769]: su - db2inst1 -c 
db2 activate database HADRDB 
 
The expected behavior is for the db2V10_start.ksh script to 
start the HADR database as the standby instead of activating it.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 and Fix Pack 5                   * 
****************************************************************

N/A

Problem was first fixed in DB2 Version 10.1 and Fix Pack 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

16.04.2015
16.07.2015
16.07.2015