|
Problem IC77699
|
Status: Closed |
UNEXPECTED DB2_KILL ISSUED BY TSA SCRIPTS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In a HADR primary failure scenario, the integrated HA solution
may perform failover so the standby database will become
primary. When the old primary is back online and available, the
solution will automatically start the old primary as the new
standby, this is called reintegration. Sometimes reintegration
is not possible if there are new connections keeping the old
primary database active. In these cases, db2_kill will be issued
internally such that the next start up of the old primary
instance will perform the reintegration successfully.
This db2_kill is working as designed, but may not be desirable
in some scenarios. This APAR will improve the reintegration code
such that it minimize the chance of db2_kill happening. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* db2 users using TSA scripts *
****************************************************************
* PROBLEM DESCRIPTION: *
* In a HADR primary failure scenario, the integrated HA *
* solution *
* may perform failover so the standby database will become *
* *
* primary. When the old primary is back online and available, *
* the *
* solution will automatically start the old primary as the new *
* *
* standby, this is called reintegration. Sometimes *
* reintegration *
* is not possible if there are new connections keeping the old *
* *
* primary database active. In these cases, db2_kill will be *
* issued *
* internally such that the next start up of the old primary *
* *
* instance will perform the reintegration successfully. *
* *
* *
* *
* *
* *
* This db2_kill is working as designed, but may not be *
* desirable *
* in some scenarios. This APAR will improve the reintegration *
* code *
* such that it minimize the chance of db2_kill happening. *
****************************************************************
* RECOMMENDATION: *
* First fixed in db2 v9.7 fixpack 5 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.07.2011
20.12.2011
20.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
