Dynamic ISM can not be locked. Please
setup oradism, or unset sga_max_size.
[diagnostic 0, 8, 268]
Permissions problems
Examine the alert log for each instance. The following entry indicates that Oracle was unable to start
the oradism process with superuser privileges:
Code: Select all
Tue Jan 24 19:54:32 2009
WARNING: -------------------------------
WARNING: oradism not set up correctly.
Dynamic ISM can not be locked. Please
setup oradism, or unset sga_max_size.
[diagnostic 0, 8, 268]
----------------------------------------
Check if the setuid bit has been set on the oradism program. For example:
Code: Select all
[code][ORCLA10 /home/oracle]$ ls -l $ORACLE_HOME/bin/oradism
-r-sr-s--- 1 root dba 14324 Apr 19 2010 /u01/app/oracle/product/10.2.0/db_1/bin/oradism
In the above example the oradism program is owned by root, and the setuid bit is set (as indicated by
the first s in rws). The program should therefore be able to start with appropriate permissions.
Oradism dies
The only likely reason why oradism might die is if a system or database administrator accidentally kills
it. Check for the presence of the oradism process with the ps program.
Unfortunately, in the unlikely event that this process dies, in Oracle Database 9i it will not be noted in
the alert log file until the next time alter system is used to grow or shrink memory.
Oracle Database10g and later releases have the ability to restart oradism if it dies. Unfortunately,
though, all SGA memory locks will have been lost, and these missing locks will not be replaced until
the database is restarted. Performance could be extremely poor in the meantime. When diagnosing the
problem, be aware that it is therefore possible to have a running oradism with root privileges, but to
have no locks (and therefore very poor performance).
SGA memory only partially locked
From Oracle Database 10g, a new table (x$ksmge) can be examined to determine the state of locks for
each granule of SGA memory (each granule is typically 16Mbytes in size for Oracle Database 10g and
64 to 512 Mbytes for Oracle Database 11g).
How to fix it
Permissions problems. Please refer to My Oracle Support Document [ID 374367.1]
Option 1: The simplest way of ensuring appropriate permissions is to make the oradism program setuid root,
obviating the need for RBAC. This can be achieved as follows:
Code: Select all
[root@dgstan ~]# chown root:dba $ORACLE_HOME/bin/oradism
[root@dgstan ~]# chmod 4550 $ORACLE_HOME/bin/oradism
[ORCLA10 /home/oracle]$ ls -l $ORACLE_HOME/bin/oradism
-r-sr-x--- 1 root dba 14324 Apr 19 2010 /u01/app/oracle/product/10.2.0/db_1/bin/oradism
-- Bounce the database.
Please note that this problem is restricted to Solaris only. This is not generic issue.
Option 2: Unset sga_max_size from your parameter file and bounce the database. This should also fix the issue.