WARNING: "oradism not set up correctly", When Setting SGA_MAX_SIZE (Doc ID 374367.1) To BottomTo Bottom
Oracle Database - Enterprise Edition - Version 9.2.0.4 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
***Checked for relevance on 07-Apr-2015***
SYMPTOMS
On Solaris platform, after enabling Automatic SGA Management (ASMM) and setting SGA_MAX_SIZE, when restarting the database, an oradism warning appears in the alert log.
The instance starts and the shared_pool_size can be changed with an alter system command.
WARNING: oradism not set up correctly.
Dynamic ISM can not be locked. Please
setup oradism, or unset sga_max_size.
[diagnostic 0, 16, 1001]
Symptoms can also include higher kernel cpu usage.
CAUSE
The real problem was with the oradism executable itself.
The oradism executable cannot have 755 (rwx-r-x-r-x) permissions, and should be owned by root like other executables in the $ORACLE_HOME/bin directory.
The permissions for oradism must be 4750 with the SetUID bit for the owner, e.g. for 11.2:
-rwsr-x--- 1 root root 1340408 Nov 17 23:05 oradism*
SOLUTION
The preferred method to set the proper permissions is to run the root.sh script as root user. This is typically done at installation time.
However, you can change the permissions as described below.
Note that some customers reported problems with the below steps. Check that you have sufficient swap configured. If swap is not sufficient, the oradism configuration can cause a crash on the box.
cd $ORACLE_HOME/bin
chown root oradism
chmod 4750 oradism
bounce the database
The oradism warning does not appear in the alert log after the permissions are changed.
Please note that this problem is restricted to Solaris only. This is not generic issue
Oracle Database - Enterprise Edition - Version 9.2.0.4 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
***Checked for relevance on 07-Apr-2015***
SYMPTOMS
On Solaris platform, after enabling Automatic SGA Management (ASMM) and setting SGA_MAX_SIZE, when restarting the database, an oradism warning appears in the alert log.
The instance starts and the shared_pool_size can be changed with an alter system command.
WARNING: oradism not set up correctly.
Dynamic ISM can not be locked. Please
setup oradism, or unset sga_max_size.
[diagnostic 0, 16, 1001]
Symptoms can also include higher kernel cpu usage.
CAUSE
The real problem was with the oradism executable itself.
The oradism executable cannot have 755 (rwx-r-x-r-x) permissions, and should be owned by root like other executables in the $ORACLE_HOME/bin directory.
The permissions for oradism must be 4750 with the SetUID bit for the owner, e.g. for 11.2:
-rwsr-x--- 1 root root 1340408 Nov 17 23:05 oradism*
SOLUTION
The preferred method to set the proper permissions is to run the root.sh script as root user. This is typically done at installation time.
However, you can change the permissions as described below.
Note that some customers reported problems with the below steps. Check that you have sufficient swap configured. If swap is not sufficient, the oradism configuration can cause a crash on the box.
cd $ORACLE_HOME/bin
chown root oradism
chmod 4750 oradism
bounce the database
The oradism warning does not appear in the alert log after the permissions are changed.
Please note that this problem is restricted to Solaris only. This is not generic issue
WARNING: oradism not setup correctly in alert log
ReplyDeleteWhen we increased the sga_max_size to 4096G in our instance, which came to a standstill because the value was 600M only, the following warning appeared in the database alert log file:
WARNING: -------------------------------
WARNING: oradism not set up correctly.
Dynamic ISM can not be locked. Please
setup oradism, or unset sga_max_size.
[diagnostic 0, 16, 64882]
----------------------------------------
Metalink note 374367.1 describes the issue and provides the solution:
The real problem was with the oradism executable itself.
The oradism executable cannot have 755 permissions, and owned by root or oracle
(rwx-r-x-r-x)like the other executables have in this directory
The permissions for oradism must be 4550 with the setid for the group.
(-r-sr-s--- 1 root dba 12912 Feb 16 2005 oradism)
(Solaris8 64-bit / oracle v9.2.0.4)
Solution
1- cd $ORACLE_HOME/bin
2- chmod 4550 oradism
3- chmod g+s oradism
4- chown root:dba oradism
5- Bounce the database
The oradism warning does not appear in the alert log after the permissions were changed.
This comment has been removed by a blog administrator.
ReplyDelete