Solaris Volume Manager (SVM) and Solaris Cluster Recover a metaset/diskset with 'stale databases' and '50% replicas 50% mediator hosts available, user intervention required'
(Doc ID 1006602.1)
Last updated on APRIL 29, 2024
Applies to:
Sun Solaris Volume Manager (SVM) - Version 11.9.0 and laterSolstice DiskSuite Software - Version 2.0.1 and later
Solaris Cluster - Version 3.0 and later
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)
Symptoms
A 2-node Solaris Cluster (SC) using Solaris Volume Manager (SVM) connected to 2 Storage Arrays. Due to a disk failure, one node panic'ed. The surviving node tried to take over the diskset but
failed to come up because the metadb (replica) database has become stale.
The cluster node won't come up because cluster framework is highly dependent on the device-group/diskset.
The following are logged in /var/adm/messages file:
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| Detailed recovery procedure if SVM diskset is used with Solaris Cluster: |
| Recovery procedure if SVM diskset is used outside of Solaris Cluster: |