The mountV105_monitor.ksh script is erroneously reporting the
mount resource as "FAILED OFFLINE" instead of "OFFLINE".
You can see the following in the db2diag.log:
2015-06-09-17.15.37.323039+060 E4604A504 LEVEL: Error
PID : 6815854 TID : 1 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME: db2host1
EDUID : 1
FUNCTION: DB2 UDB, high avail services,
sqlhaCreateMountInternal, probe:9949
MESSAGE : Please ensure mount object is in correct state
DATA #1 : String, 9 bytes
db2host1
DATA #2 : String, 20 bytes
db2mnt-db2_db2inst1-rs
DATA #3 : String, 9 bytes
db2host1
DATA #4 : String, 15 bytes
db2_db2inst1_0-rs
The issue as already stated is that the mount resource is
reporting as failed offline on host db2host1:
Jun 9 17:15:34 db2host1 user:debug
mountV105_monitor.ksh[11730972]: backgrounding the stop force
for /db2/db2inst1
Jun 9 17:15:34 db2host1 user:debug
mountV105_monitor.ksh[11730972]: Returning 3 for mount
/db2/db2inst1
As a result, the db2haicu utility may fail to add the mount
resource with the following error:
Enter the full path of the mount you wish to add to the cluster:
/db2/db2inst1
Which DB2 database partition should the path '/db2/db2inst1' be
associated with?
0
Adding mount point '/db2/db2inst1' to the cluster ...
There was an error with one of the issued cluster manager
commands. The user can determine the cause of the error by
invoking 'db2instance -list' and 'db2cluster -list -alert'. The
db2diag.log for the current member and the DB2 Information
Center may provide additional details. |
