Oracle Enterprise Manager 10g is a powerful tool that comes with many administrative features which make database management much more simpler.
It has an inbuilt job scheduler that lets you schedule jobs. Its not a very feature rich scheduler but still does quite a lot considering the fact that it is free with Oracle's License.
I am outlining a configuration problem that may save some time to diagnose:
If a shell script or a Java program is executed using OEM under the credentials of a user who doesnt belong to the Oracle user group on Solaris, it fails with the following error:
Shell script :
/bin/sh: cannot determine current directory
or
shell-init: could not get current directory: getcwd: cannot access parent directories: Permission denied
Java Proram :
Error occurred during initialization of VM
java.lang.Error: Properties init: Could not determine current working directory
This is due to permission lacking on the directory where the OEM agent is installed
/u01/app/oracle/product/agent10g/sysman/emd
Check the permissions on this directory.
drwxr-x--- 6 oracle dba 512 May 12 13:40 emd
Change the permissions to
drwxr-xr-x 6 oracle dba 512 May 12 13:40 emd
I believe that OEM's working directory is the above location and since the underlying user doesnt have access to this directory, hence all the programs error out.
It has an inbuilt job scheduler that lets you schedule jobs. Its not a very feature rich scheduler but still does quite a lot considering the fact that it is free with Oracle's License.
I am outlining a configuration problem that may save some time to diagnose:
If a shell script or a Java program is executed using OEM under the credentials of a user who doesnt belong to the Oracle user group on Solaris, it fails with the following error:
Shell script :
/bin/sh: cannot determine current directory
or
shell-init: could not get current directory: getcwd: cannot access parent directories: Permission denied
Java Proram :
Error occurred during initialization of VM
java.lang.Error: Properties init: Could not determine current working directory
This is due to permission lacking on the directory where the OEM agent is installed
/u01/app/oracle/product/agent10g/sysman/emd
Check the permissions on this directory.
drwxr-x--- 6 oracle dba 512 May 12 13:40 emd
Change the permissions to
drwxr-xr-x 6 oracle dba 512 May 12 13:40 emd
I believe that OEM's working directory is the above location and since the underlying user doesnt have access to this directory, hence all the programs error out.
No comments:
Post a Comment