Thursday, November 1, 2012

oradism creation failed for unknown reasons 0 8 11001

On Solaris box, whenever we started database instance, we saw multiple occurrences of below warnings. This started after we setup Automatic Memory Management feature of 11g (memory_target).



WARNING: -------------------------------
WARNING: oradism did not start up correctly.
  Dynamic ISM can not be locked.----------------------------------------
oradism creation failed for unknown reasons 0 8 11001
Tue Oct 30 06:47:00 2012
WARNING: Detected too many memory locking problems.
WARNING: Performance degradation may occur.
 
First thing I checked was file permissions on $ORACLE_HOME/bin/oradism.

It was owned by oracle with 750 permissions.

The oradism utility SHOULD be owned by root with 4755 permissions.

Then I also realized that some other utilities like extjob are also owned by oracle instead of root.

This made me believe that the root.sh was not run. Root.sh script takes care of changing ownership and permissions on some these utilities.

We ran root.sh as root user and that did it. Now we are not seeing above warnings anymore in the alert log of databases.

1 comment:

  1. Does this Warning only get logged on Solaris or is RHEL 5/6 also affected?

    We have Oracle 11g running in a Solaris Cluster as a resource and found this Warning logged when the Oracle resource moved nodes in our cluster. Updating the ownerships and permissions fixed the logged Warnings, thank you. I checked the 'root.sh' script and it updates ownership to root permissions to 4750, not 4755 as suggested, but all utilities appear correct now.

    Thank you for the great post!

    ReplyDelete