suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT15249 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 / 970 - DB2
Problem description:
In the event of a primary server failure, the IBM.Test
Reintegration flag is being created after the db2V97_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 db2V97_start.ksh[2769]: Entered
/usr/sbin/rsct/sapolicies/db2/db2V97start.ksh, db2inst1, 0
Mar 13 15:42:55 host4 db2V97_start.ksh[2774]: Able to cd to
/home/db2inst1/sqllib :
/usr/sbin/rsct/sapolicies/db2/db2V97_start.ksh, db2inst1, 0
Mar 13 15:42:56 host4 db2V97_start.ksh[2776]: 1 partitions
total: /usr/sbin/rsct/sapolicies/db2/db2V97_start.ksh,
db2inst1, 0
Mar 13 15:43:01 host4 db2V97_start.ksh[2784]:  Returning 0 from
/usr/sbin/rsct/sapolicies/db2/db2V97_start.ksh ( db2inst1, 0)

The expected behavior is for the db2V97_start.ksh script to
start the HADR database as the standby instead of activating it,
in which case you would expect to see the following syslog
messages logged by the db2V97_start.ksh script:

Mar 13 16:00:08 host4 db2V97_start.ksh[15794200]: Forcing apps
off before reintegration
Mar 13 16:00:09 host4 db2V97_start.ksh[15794204]: After forcing,
starting to reintegrate
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fixpack of DB2 V10.5 or V11.1.         *
****************************************************************
Local Fix:
N/A
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT08004 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.05.2016
01.03.2017
01.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)