WARNING: oradism not set up correctly. Dynamic ISM can not be locked. Please setup oradism, or unset sga_max_size

========================================================================
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 (32bit)
Oracle Solaris on SPARC (64bit)
Oracle Solaris on x8664
(64bit)
z*OBSOLETE: Fujitsu PRIMEPOWER Solaris
Oracle Solaris on SPARC (32bit)
z*OBSOLETE: Sun Trusted Solaris (Secure)
Fujitsu PRIMEPOWER Solaris
Sun Solaris x86 (32bit)
Sun Solaris SPARC (64bit)
Sun Trusted Solaris (Secure)
Sun Solaris x8664
(64bit)
Sun Solaris SPARC (32bit)
========================================================================
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:
ORA01115:
IO error reading block from file 11 (block # 722525)
ORA01110:
data file 11: '+DATA1/dev3/datafile/development.8115.666100645'
ORA15078:
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:
ORA00340:
IO error processing online log 1 of thread 1
ORA00345:
redo log write error block 11022 count 12
ORA00312:
online log 1 thread 1: '+DATA1/dev3/onlinelog/group_1.8102.666102843'
ORA15078:
ASM diskgroup was forcibly dismounted
Tue Sep 23 21:03:56 2008
LGWR: terminating instance due to error 340

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.
========================================================================

CAUSE:
These errors and were caused by an improper setup for 'oradism'.
The file permissions for the executable '$ORACLE_HOME/bin/oradism' were not properly set possibly
due to
'root.sh' was not executed after Oracle Universal Installer (OUI) installed the Oracle Home, however this could not
be validated.
========================================================================
Solution:
After fixing the file permissions of '$ORACLE_HOME/bin/oradism' the database instance the issue has stopped.
The permissions for 'oradism' must be 6550 with the setid for the group:
e.g. (rsrs1
root oinstall 129 12 Feb 16 2008 oradism)
========================================================================
Reference: ASM Forcibly Dismounts Diskgroups or Causes Disks to be Offlined If 'oradism' is
Improperly Set (Doc ID 744869.1)