I am trying to set up HADR to run on my DB2 10.5 DB2 servers. I believe I have followed the steps correctly, but I'm getting the following error:
[db2insh1@rslvm20 OneView]$ db2 restore database onevwhad
DB20000I The RESTORE DATABASE command completed successfully.
[db2insh1@rslvm20 OneView]$ db2 -vtf update_config_HADR_Secondary.sql
UPDATE DB CFG FOR ONEVWHAD USING HADR_LOCAL_HOST rslvm20.dub.usoh.ibm.com HADR_LOCAL_SVC DB2_db2insh1_hadr HADR_SYNCMODE NEARSYNC HADR_REMOTE_HOST rslvm19.dub.usoh.ibm.com HADR_REMOTE_SVC DB2_db2insh1_hadr HADR_REMOTE_INST db2insh1
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
[db2insh1@rslvm20 OneView]$ db2 start hadr on db onevwhad as standby
SQL1767N Start HADR cannot complete. Reason code = "1".
The Knowledge Center says this about that error:
Start HADR cannot complete. The explanation corresponding to the reason code is:
1: The database was not in roll forward-pending or roll forward-in-progress state
when the START HADR AS STANDBY command was issued.
The user response corresponding to the reason code is:
1: Initialize the standby database from a backup image or a split mirror of the
primary database, then reissue the START HADR AS STANDBY command.
But I restored the database right before I updated the HADR config, and then tried to start HADR. There were no intervening steps, so I am confused. I'm fairly sure I have to update the config between restoring the DB and starting HADR. Any idea what I'm doing wrong?
==========================================================================================
The 'LOGARCHMETH1' option is set to 'OFF'.
Here are the applicable contents from db2diag.log. It doesn't tell me (with my limited knowledge) anything other than the -1767 error code.
2014-12-04-11.46.29.565620-300 I228560E692 LEVEL: Event
PID : 32654 TID : 140560786515712 PROC : db2sysc 0
INSTANCE: db2insh1 NODE : 000 DB : ONEVWHAD
APPHDL : 0-200 APPID: *LOCAL.db2insh1.141204164629
AUTHID : DB2INSH1 HOSTNAME: rslvm20.dub.usoh.ibm.com
EDUID : 22 EDUNAME: db2agent (ONEVWHAD) 0
FUNCTION: DB2 UDB, base sys utilities, sqleCalculateDbHeaps, probe:70
MESSAGE : RLMS - DB Memory Set for Resident Member
DATA #1 : String, 10 bytes
totalBytes
DATA #2 : unsigned integer, 8 bytes
236519424
DATA #3 : String, 11 bytes
dbHeapBytes
DATA #4 : unsigned integer, 8 bytes
164298752
2014-12-04-11.46.29.594451-300 I229253E673 LEVEL: Error
PID : 32654 TID : 140560786515712 PROC : db2sysc 0
INSTANCE: db2insh1 NODE : 000 DB : ONEVWHAD
APPHDL : 0-200 APPID: *LOCAL.db2insh1.141204164629
AUTHID : DB2INSH1 HOSTNAME: rslvm20.dub.usoh.ibm.com
EDUID : 22 EDUNAME: db2agent (ONEVWHAD) 0
FUNCTION: DB2 UDB, data protection services, sqlpPrepareAndValidateEnvForHadr, probe:540
MESSAGE : ZRC=0x8010006D=-2146434963=SQLP_RC_CA_BUILT
"SQLCA has been built and saved in component specific control block."
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-1767
2014-12-04-11.46.29.594815-300 I229927E600 LEVEL: Error
PID : 32654 TID : 140560786515712 PROC : db2sysc 0
INSTANCE: db2insh1 NODE : 000 DB : ONEVWHAD
APPHDL : 0-200 APPID: *LOCAL.db2insh1.141204164629
AUTHID : DB2INSH1 HOSTNAME: rslvm20.dub.usoh.ibm.com
EDUID : 22 EDUNAME: db2agent (ONEVWHAD) 0
FUNCTION: DB2 UDB, data protection services, sqlpinit, probe:1050
MESSAGE : ZRC=0x8010006D=-2146434963=SQLP_RC_CA_BUILT
"SQLCA has been built and saved in component specific control block."
2014-12-04-11.46.29.595098-300 I230528E936 LEVEL: Severe
PID : 32654 TID : 140560786515712 PROC : db2sysc 0
INSTANCE: db2insh1 NODE : 000 DB : ONEVWHAD
APPHDL : 0-200 APPID: *LOCAL.db2insh1.141204164629
AUTHID : DB2INSH1 HOSTNAME: rslvm20.dub.usoh.ibm.com
EDUID : 22 EDUNAME: db2agent (ONEVWHAD) 0
FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::FirstConnect, probe:9831
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1767 sqlerrml: 1
sqlerrmc: 1
sqlerrp : sqlpPrep
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
DATA #2 : Boolean, 1 bytes
false
Here are the config values for HADR on my standby, if they matter:
UPDATE DB CFG FOR ONEVWHAD USING
HADR_LOCAL_HOST rslvm20.dub.usoh.ibm.com
HADR_LOCAL_SVC DB2_db2insh1_hadr
HADR_SYNCMODE NEARSYNC
HADR_REMOTE_HOST rslvm19.dub.usoh.ibm.com
HADR_REMOTE_SVC DB2_db2insh1_hadr
HADR_REMOTE_INST db2insh1
And on the primary:
UPDATE DB CFG FOR ONEVWHAD USING
HADR_LOCAL_HOST rslvm19.dub.usoh.ibm.com
HADR_LOCAL_SVC DB2_db2insh1_hadr
HADR_SYNCMODE NEARSYNC
HADR_REMOTE_HOST rslvm20.dub.usoh.ibm.com
HADR_REMOTE_SVC DB2_db2insh1_hadr
HADR_REMOTE_INST db2insh1
BTW, I think the restore is working, because I can see the data from the primary in the tables in the standbay.
Best Answer
I got the exactly same error message and logs in db2diag.log, what I did to solve this issue is don't do the roll forwarding after the restore, must keep the restored DB in roll forwarding pending status, then you can start HADR on it.