Solaris Cluster 3.3u1 HAStoragePlus Validation Errors due to similar filesystem mountpoints after Upgrade to 3.3u1 (Doc ID 1462553.1)

Last updated on JUNE 27, 2017

Applies to:

Solaris Cluster - Version 3.3 U1 to 3.3 U2 [Release 3.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
'Validation failed as one of the mount device or pool of this resource is being managed by other resource'

Symptoms

After upgrading Solaris Cluster 3.2U1 -> 3.3U1.  HAStoragePlus validations are seen upon making any changes to Resource.


Error seen:

In /etc/vfstab, the mount points for oracle is the same on all nodes, however, the metaset diskset names are different, because 2 nodes are in one DC (Data Center) and the other 2 in a second DC. Dataguard is setup and logs are shipped from one DC to the other.

Nodes 110 and 101 are in DC1
Nodes 109 and 102 are in DC2

 
Node 110:
### PLD

/dev/md/00e-ms/dsk/d10 /dev/md/00e-ms/rdsk/d10 /apps/sap/PLDDB/oracle/PLD/origlogA ufs 3 no logging,forcedirectio
/dev/md/00e-ms/dsk/d20 /dev/md/00e-ms/rdsk/d20 /apps/sap/PLDDB/oracle/PLD/origlogB ufs 3 no logging,forcedirectio
/dev/md/00e-ms/dsk/d30 /dev/md/00e-ms/rdsk/d30 /apps/sap/PLDDB/oracle/PLD/mirrlogA ufs 3 no logging,forcedirectio

Node 101:
### PLD

/dev/md/00e-ms/dsk/d10 /dev/md/00e-ms/rdsk/d10 /apps/sap/PLDDB/oracle/PLD/origlogA ufs 3 no logging,forcedirectio
/dev/md/00e-ms/dsk/d20 /dev/md/00e-ms/rdsk/d20 /apps/sap/PLDDB/oracle/PLD/origlogB ufs 3 no logging,forcedirectio
/dev/md/00e-ms/dsk/d30 /dev/md/00e-ms/rdsk/d30 /apps/sap/PLDDB/oracle/PLD/mirrlogA ufs 3 no logging,forcedirectio


Node 109:
#### PLD

/dev/md/00c-ms/dsk/d10 /dev/md/00c-ms/rdsk/d10 /apps/sap/PLDDB/oracle/PLD/origlogA ufs 3 no logging,forcedirectio
/dev/md/00c-ms/dsk/d20 /dev/md/00c-ms/rdsk/d20 /apps/sap/PLDDB/oracle/PLD/origlogB ufs 3 no logging,forcedirectio
/dev/md/00c-ms/dsk/d30 /dev/md/00c-ms/rdsk/d30 /apps/sap/PLDDB/oracle/PLD/mirrlogA ufs 3 no logging,forcedirectio
/dev/md/00c-ms/dsk/d40 /dev/md/00c-ms/rdsk/d40 /apps/sap/PLDDB/oracle/PLD/mirrlogB ufs 3 no logging,forcedirectio

Node 102:
#### PLD

/dev/md/00c-ms/dsk/d10 /dev/md/00c-ms/rdsk/d10 /apps/sap/PLDDB/oracle/PLD/origlogA ufs 3 no logging,forcedirectio
/dev/md/00c-ms/dsk/d20 /dev/md/00c-ms/rdsk/d20 /apps/sap/PLDDB/oracle/PLD/origlogB ufs 3 no logging,forcedirectio
/dev/md/00c-ms/dsk/d30 /dev/md/00c-ms/rdsk/d30 /apps/sap/PLDDB/oracle/PLD/mirrlogA ufs 3 no logging,forcedirectio
/dev/md/00c-ms/dsk/d40 /dev/md/00c-ms/rdsk/d40 /apps/sap/PLDDB/oracle/PLD/mirrlogB ufs 3 no logging,forcedirectio

Changes

 Issue seen after upgrade to Solaris Cluster 3.3u1 5/11

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms