Attempting to move HADR databases for scheduled maintenance via
db2haicu maintenance mode menu option 5 may fail for some
databases:
Select an administrative task by number from the list below:
1. Add or remove cluster nodes.
2. Add or remove a network interface.
3. Add or remove HADR databases.
4. Add or remove an IP address.
5. Move DB2 database partitions and HADR databases for
scheduled maintenance.
6. Create a new quorum device for the domain.
7. Destroy the domain.
8. Exit.
Enter your selection:
5
Do you want to review the status of each cluster node in the
domain before you begin? [1]
1. Yes
2. No
2
Enter the name of the node away from which DB2 partitions and
HADR primary roles should be moved:
HOST1
Cluster node 'HOST1' hosts the following resources associated
with the database manager instance 'db2inst1':
HADR Database: HADRDBZ
HADR Database: HADRDBY
HADR Database: HADRDBX
HADR Database: HADRDBW
HADR Database: HADRDBU
All of these cluster resource groups will be moved away from the
cluster node 'HOST1'. This will take their database partitions
offline for the duration of the move, or cause an HADR role
switch for HADR databases. Clients will experience an outage
from this process. Are you sure you want to continue? [1]
1. Yes
2. No
1
Submitting move request for resource group
'db2_db2inst1_db2inst1_HADRDBZ-rg' ...
The move request for resource group
'db2_db2inst1_db2inst1_HADRDBZ-rg' was submitted successfully.
Submitting move request for resource group
'db2_db2inst1_db2inst1_HADRDBY-rg' ...
The move request for resource group
'db2_db2inst1_db2inst1_HADRDBY-rg' was submitted successfully.
Submitting move request for resource group
'db2_db2inst1_db2inst1_HADRDBX-rg' ...
The move request for resource group
'db2_db2inst1_db2inst1_HADRDBX-rg' was submitted successfully.
Submitting move request for resource group
'db2_db2inst1_db2inst1_HADRDBW-rg' ...
Moving resource group failed. Refer to db2diag.log for the
current member and the DB2 Information Center for details.
Submitting move request for resource group
'db2_db2inst1_db2inst1_HADRDBU-rg' ...
The move request for resource group
'db2_db2inst1_db2inst1_HADRDBU-rg' was submitted successfully.
The following errors will be seen in the db2diag.log file:
2017-04-25-07.43.15.001881+120 E661165A3014 LEVEL: Error
PID : 21889476 TID : 27498 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-4728 APPID:
*LOCAL.db2inst1170425054134
AUTHID : DB2INST1 HOSTNAME: HOST2
EDUID : 27498 EDUNAME: db2agent (HADRDBW) 0
FUNCTION: DB2 UDB, high avail services,
sqlhaWaitForResourceState, probe:16314
DATA #1 : String, 24 bytes
db2_db2inst1_db2inst1_HADRDBW-rs
DATA #2 : String, 0 bytes
Object not dumped: Address: 0x0A0000003CBD2924 Size: 0 Reason:
Zero-length data
DATA #3 : signed integer, 4 bytes
17
DATA #4 : signed integer, 4 bytes
1
DATA #5 : SQLHA Control Block, PD_TYPE_SQLHA_CONTROL_BLOCK, 4160
bytes
sqlhaCB->timeout: 88
sqlhaCB->runMode: INFRASTRUCTURE
sqlhaCB->options: NONE
sqlhaCB->vendorHandle: 000000011ba895c0
sqlhaCB->sqlhaClusterHandle->clusterHandle: 1
sqlhaCB->sqlhaClusterHandle->clusterFlags: 0
sqlhaCB->sqlhaClusterHandle->clusterErrorNum: 0
sqlhaCB->sqlhaClusterHandle->errorMessage:
sqlhaCB->sqlhaClusterHandle->clusterCommand:
DATA #6 : ZRC, PD_TYPE_ZRC, 4 bytes
0x87000057
DATA #7 : SQLHA Cluster Session Handle,
PD_TYPE_SQLHA_CLUSTER_HANDLE, 4120 bytes
sqlhaClusterHandle->clusterHandle: 1
sqlhaClusterHandle->clusterFlags: 0
sqlhaClusterHandle->clusterErrorNum: 0
sqlhaClusterHandle->errorMessage:
sqlhaClusterHandle->clusterCommand:
DATA #8 : signed integer, 4 bytes
0
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0900000011605B2C
sqlhaWaitForResourceState__FP25SQLHA_CLUSTER_OBJECT_INFO15_sqlha
ObjStatesP19SQLHA_CONTROL_BLOCK + 0x540
[1] 0x090000000C55B894
sqlhaEnableClusterAutomationForHADRResource__FP16sqeLocalDatabas
eP19SQLHA_CONTROL_BLOCK + 0xED4
[2] 0x090000000E2FA930
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0x43290
[3] 0x090000000E2F0724
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0x39084
[4] 0x090000000E2207FC
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0xF54
[5] 0x090000000E201914
sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x604
[6] 0x090000000FF30864
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x644
[7] 0x090000000FF198E0
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x11E4
[8] 0x090000000FF198E0
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x11E4
[9] 0x090000000FF194D4
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xDD8
[10] 0x0900000010C874E4
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8
[11] 0x0900000010C87FF8
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5FC
[12] 0x09000000106D795C RunEDU__8sqeAgentFv + 0x40E1C
[13] 0x090000001064C738 RunEDU__8sqeAgentFv + 0x124
[14] 0x090000000F461AE4 EDUDriver__9sqzEDUObjFv + 0x130
[15] 0x090000000F0F32D4 sqloEDUEntry + 0x3A0
[16] 0x0900000000509E10 _pthread_body + 0xF0
[17] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
2017-04-25-07.43.15.003350+120 E664180A713 LEVEL: Error
PID : 21889476 TID : 27498 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-4728 APPID:
*LOCAL.db2inst1.170425054134
AUTHID : DB2INST1 HOSTNAME: HOST2
EDUID : 27498 EDUNAME: db2agent (HADRDBW) 0
FUNCTION: DB2 UDB, high avail services, sqlhaEnableHADRResource,
probe:14174
MESSAGE : ZRC=0x87000057=-2030043049=SQLZ_RC_TIMEOUT "Action
timed out"
DIA8578C A timeout occurred while waiting on a
semaphore.
DATA #1 : String, 47 bytes
Unable to verify HADR resource state as online.
DATA #2 : String, 24 bytes
db2_db2inst1_db2inst1_HADRDBW-rs |
