|
Problem IT30788
|
Status: Closed |
HADR CANNOT BE STARTED DUE TO INSUFFICIENT HADR DATABASE RESOURCE VALIDATION
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
When starting HADR on a database with certain TSA automation
already
enabled in the cluster, it may fail with error message in
db2diag.log:
"SQL1768N Unable to start HADR. Reason code = 29 29 Either
change hadr_syncmode database configuration to SYNC or NEARSYNC,
or disable automated failover via db2haicu." |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to v111m4fp5 *
**************************************************************** |
| Local Fix: |
Disable automation on both active-passive pairs, and start
HADR, and re-enable automation again. |
| Solution |
|
| Workaround |
see local fix |
| BUG-Tracking |
forerunner : IT29225
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.10.2019
31.10.2019
31.10.2019 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
