DB2 - Problem description
Problem IT08371 | Status: Closed |
IN A HADR HA(TSA) ENVIRONMENT, IN THE EVENT OF A PRIMARY SERVER FAILURE, THE STANDBY MAY NOT BE REINTEGRATED ON INSTANCE STARTUP | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 and Fix Pack 5 * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.04.2015 16.07.2015 16.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |