|
Problem IT07145
|
Status: Geschlossen |
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 |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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. |
| Lösung |
First Fixed in DB2 LUW v10.5 Fixpack 7. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.02.2015
20.01.2016
20.01.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.7
|
 |
