ASM Forcibly Dismounts Diskgroups or Causes Disks to be Offlined If 'oradism' is Improperly Set
(Doc ID 744869.1)
Last updated on DECEMBER 20, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Solaris on x86 (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
z*OBSOLETE: Fujitsu PRIMEPOWER Solaris
Oracle Solaris on SPARC (32-bit)
z*OBSOLETE: Sun Trusted Solaris (Secure)
Fujitsu PRIMEPOWER Solaris
Sun Solaris x86 (32-bit)
Sun Solaris SPARC (64-bit)
Sun Trusted Solaris (Secure)
Sun Solaris x86-64 (64-bit)Sun Solaris SPARC (32-bit)
***Checked for relevance on 18-Apr-2013***
* The environment in this case was: Single-Instance/Standalone (non-RAC) - 10203 - Solaris Operating Systems (SPARC 64-bit)
* 'oradism' is Oracle's implementation of the Solaris specific 'Dynamic Intimate Shared Memory' feature
An ASM instance intermittently loses contact with some of its ASM disks.
The affected disks will be offlined and possibly cause ASM diskgroups to be forcibly dismounted.
The ASM alert log shows:
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