|
Problem IT07145
|
Status: Closed |
IN A HADR HA(TSA) ENVIRONMENT, IN THE EVENT OF A PRIMARY SERVER FAILURE, THERE MAY BE A DELAY IN REINTEGRATING THE DB AS STANDBY |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In an automated HADR HA(TSA) environment, in the case where
there is a failure on the primary server, DB2 will automatically
be restarted by TSA. During DB2 start processing, there may be a
15 minute delay in reintegrating the old primary db as the new
standby.
In this case, the following message will be seen periodically at
5 second intervals in the syslogs of the failing machine during
DB2 startup:
Feb 9 08:52:07 host01 user:info db2V105_start.ksh[12648578]: su
- db2inst1 -c db2 activate database HADRDB
Feb 9 08:52:13 host01 user:info db2V105_start.ksh[12648578]: su
- db2inst1 -c db2 activate database HADRDB
Feb 9 08:52:18 host01 user:info db2V105_start.ksh[12648578]: su
- db2inst1 -c db2 activate database HADRDB
Feb 9 08:52:23 host01 user:info db2V105_start.ksh[12648578]: su
- db2inst1 -c db2 activate database HADRDB |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW v10.5 Fixpack 7 or Later. *
**************************************************************** |
| Local Fix: |
Contact IBM support for a fix. |
| Solution |
First Fixed in DB2 LUW v10.5 Fixpack 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.02.2015
20.01.2016
20.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
