|
Problem IT08308
|
Status: Closed |
IN AN AUTOMATED HADR ENVIRONMENT, FOLLOWING A REBOOT OF THE STAN DBY SERVER, THE DATABASE MAY NOT BE REINTEGRATED AS THE STANDBY |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In an automated HADR environment, whereby a virtual IP address
is not used for database client connections, it is possible for
the HADR database to be mistakenly queried as activated at
instance startup time and as a result the database is not
activated.
This is a result of database client connections attempting to
connect to the standby database. If a Virtual IP address is used
by database client connections, then this issue is avoidable.
If this issue is reproduced, then the following syslog message
will be seen on the standby at instance startup time:
Mar 3 16:23:23 host01 user:info db2V105_start.ksh[11206778]:
deact == 0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* HADR/TSA users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.5 FP7 *
**************************************************************** |
| Local Fix: |
Manually activate the HADR database on the standby server. |
| Solution |
Fixed in DB2 V10.5 FP7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.04.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
|
 |
