ASM Forcibly Dismounts Diskgroups or Causes Disks to be Offlined If 'oradism' is Improperly Set (Doc ID 744869.1)

Last updated on APRIL 18, 2013

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]
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***

Symptoms

Comments:
* 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:

Tue Sep 23 21:03:55 2008
WARNING: offlining disk 1.3765258242 (SAN06) with mask 0x3
NOTE: PST update: grp = 1, dsk = 1, mode = 0x6
NOTE: PST update: grp = 1, dsk = 1, mode = 0x4
NOTE: cache closing disk 1 of grp 1: SAN06
WARNING: offlining disk 4.3765258240 (SAN02) with mask 0x3
NOTE: PST update: grp = 1, dsk = 4, mode = 0x6
Tue Sep 23 21:03:55 2008
ERROR: too many offline disks in PST (grp 1)
Tue Sep 23 21:03:55 2008
ERROR: PST-initiated MANDATORY DISMOUNT of group DATA1
NOTE: cache dismounting group 1/0x75BDB70D (DATA1)
Tue Sep 23 21:03:55 2008
NOTE: halting all I/Os to diskgroup DATA1
Tue Sep 23 21:03:56 2008
SUCCESS: diskgroup DATA1 was dismounted

The database alert log will show:

Tue Sep 23 21:03:55 2008
SUCCESS: diskgroup DATA1 was dismounted
SUCCESS: diskgroup DATA1 was dismounted
Tue Sep 23 21:03:55 2008
Errors in file /u01/app/oracle/product/10.2.0/db_
dev3/admin/DEV3/bdump/dev3_j000_1012.trc:
ORA-01115: IO error reading block from file 11 (block # 722525)
ORA-01110: data file 11: '+DATA1/dev3/datafile/development.8115.666100645'
ORA-15078: ASM diskgroup was forcibly dismounted
...
...<more of the above for file 1 as well, different blocks>
...
Tue Sep 23 21:03:56 2008
Errors in file /u01/app/oracle/product/10.2.0/db_dev3/admin/DEV3/bdump/dev3_l
gwr_14502.trc:
ORA-00340: IO error processing online log 1 of thread 1
ORA-00345: redo log write error block 11022 count 12
ORA-00312: online log 1 thread 1: '+DATA1/dev3/onlinelog/group_1.8102.666102843'
ORA-15078: ASM diskgroup was forcibly dismounted
Tue Sep 23 21:03:56 2008
LGWR: terminating instance due to error 340

Immediately after the instance start up or sometimes after some time, the following errors will present themselves in the alert file and before the ASM drops the disks and forcibly dismounts the disk group:

WARNING: -------------------------------
WARNING: oradism not set up correctly.
Dynamic ISM can not be locked. Please
setup oradism, or unset sga_max_size.
[diagnostic 0, 8, 101]
----------------------------------------
...
WARNING: Detected too many memory locking problems.
WARNING: Performance degradation may occur.

Note:  Around the time of the error, no entries of concerning nature were found within the OS system log file or within the SAN storage log files.  To recover from the issue, adding back the disks to the ASM diskgroup is necessary.

Changes

This problem was reported soon after the database was migrated from the file system storage to ASM.

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