Symptoms:
You have copied/movied to another disk or location the Oracle binary files that were already installed, after that you cannot startup the instance that raises an error.
Cause:
During the copy/move of files, it was not preserved the file system permissions.
Solution:
There are couple of reasons why the error can report for a new software installation.
1.) root.sh was not run as part of the installation.
2.) The permissions are not set correctly on oradism or the oracle process.
[oracle@localhost bin]$ ls -ltr $ORACLE_HOME/bin/oracle
-rwxr-x--x 1 grid oinstall 474620976 Feb 9 11:45 /u01/app/21.0.0.0/grid/bin/oracle
[oracle@localhost bin]$ ls -l oradism
-rwsr-x---. 1 root oinstall 1882760 Oct 7 07:57 oradism
For oracle, the file permission should be 6751
chmod 6751 oracle
For oradism, file permission should be 4750
chmod 4750 oradism
3.) The startup command run from another user which is not part of the “oradism” group.
4.) The oracle binary's group is different than oradism's group. Both should match.
[oracle@localhost bin]$ ls -l oracle
-rwsr-s--x. 1 oracle oinstall 536007304 Jan 27 09:13 oracle
[oracle@localhost bin]$ ls -l oradism
-rwsr-x---. 1 root oinstall 1882760 Oct 7 07:57 oradism
5.) Another possible scenario for this problem :
The mount having the oradism binary is having "nosuid" option set.
With which even if the permissions are proper and kernel configurations are fine, the oradism execution as root user will not be honored by root.
Check the mount (or /etc/fstab) for this case.
Hope this help.
References:
Doc ID 2929596.1 - ORA-12791 Even if oradism Permissions Seems Correct
No comments:
Post a Comment