DB2 - Problem description
| Problem IT02964 | Status: Closed |
DB2 ROLLING UPDATE GIVES SQL1770N TAKEOVER HADR CANNOT COMPLETE. REASON CODE = "7" WHILE TAKE OVER COMMAND | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
While doing rolling update,take over command gives communication
error e.g:-
[db2v10@ts-test db2dump]$ db2 takeover hadr on db hadr
SQL1770N Takeover HADR cannot complete. Reason code = "7".
db2diag.log entry:-
2014-06-05-15.56.20.669781-300 I555680A573 LEVEL: Error
PID : 21889254 TID : 4113 PROC
:db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
sample
APPHDL : 0-9 APPID:
*LOCAL.db2inst1.140605205608
AUTHID : db2inst1 HOSTNAME: test
EDUID : 4113 EDUNAME: db2agent (Z41) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrTakeoverHdrRouteIn, probe:55610
RETCODE : ZRC=0x8280001B=-2105540581=HDR_ZRC_COMM_CLOSED
"Communication with HADR partner was lost"
2014-06-05-15.56.22.097635-300 I556708A642 LEVEL: Error
PID : 21889254 TID : 10282 PROC
:db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
sample
HOSTNAME: test
EDUID : 10282 EDUNAME: db2hadrp.0.1 (Z41) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrVerifySystem, probe:15510
MESSAGE : ZRC=0x87800140=-2021654208=HDR_ZRC_CONFIGURATION_ERROR
"One or both databases of the HADR pair is configured
incorrectly"
DATA #1 : <preformatted>
The db2 release level on this machine, SQL10014, is different
from that on the remote machine, SQL10013.
2014-06-05-15.56.22.098522-300 E557351A677 LEVEL: Error
PID : 21889254 TID : 10282 PROC
:db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
sample
HOSTNAME: test
EDUID : 10282 EDUNAME: db2hadrp.0.1 (Z41) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrVerifySystem, probe:15510
MESSAGE : ADM12502E Unable to establish HADR primary-standby
connection because the DB2 versions do not match the primary and
standby databases. Upgrade the DB2 software to the same
release and FixPak on either the HADR primary or HADR standby
database to
match the other. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 Fix Pack 5 * **************************************************************** | |
| Local Fix: | |
| Solution | |
First fixed in DB2 10.1 Fix Pack 5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.07.2014 17.02.2017 17.02.2017 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|