"ORA-12012: error on auto execute of job ORACLE_OCM.MGMT_CONFIG_JOB_2_1" And "ORA-29280: invalid dir
"ORA-12012: error on auto execute of job ORACLE_OCM.MGMT_CONFIG_JOB_2_1" And "ORA-29280: invalid directory path" In Database AlertLog (Doc ID 1453959.1)
In this Document
OracleConfiguration Manager - Version 10.3.3.0.0 and later
Informationin this document applies to any platform.
Followingerror is reported every 24 hours in the alertLog file of a 18.104.22.168 database:
Errorsin file /opt/oracle/diag/rdbms/db/trace/db_j001_26027.trc:
ORA-12012: error on auto execute of job"ORACLE_OCM"."MGMT_CONFIG_JOB_2_1"
ORA-29280: invalid directory path
ORA-06512:at "ORACLE_OCM.MGMT_DB_LL_METRICS", line 2436
ORA-06512:at line 1
Newlyinstalled 22.214.171.124 database, or recently upgraded to 126.96.36.199 from an earlierrelease.
Newerdatabase releases are automatically instrumented for OCM collections. But here,the OCM instrumentation job is trying to write to a "state" directorywhich doesn't yet exists.
To verifythe OCM db directories, run as sysdba:
SQL>select* from dba_directories where DIRECTORY_NAME like '%OCM_CONFIG%';
MGMT_DB_LL_METRICSwants to write to ORACLE_OCM_CONFIG_DIR2, which is not created by the built-ininstrumentation scripts.
Problem isfixed with OCM Collector version 10.3.7
A. But out-of-box the 11.2 databaseincludes earlier OCM version, therefore one must re-configure database for OCMcollections by running the"ORACLE_HOME/ccr/admin/scripts/installCCRSQL" script. If script ismissing, first configure OCM by running"ORACLE_HOME/ccr/bin/setupCCR".
Pay attention when on RAC database, with a non-sharedfile system environment, must set the ORACLE_CONFIG_HOME environment variableto $ORACLE_HOME prior to running the installCCRSQL.sh script. Reference: Oracle Configuration Manager Installation andAdministration Guide
B. when not using the OCM Collector,remove the OCM objects from database:
SQL>drop user ORACLE_OCM cascade;
OCM is astandalone, separate tool and removing won't affect the database functionality.
Or couldsimply disable the OCM jobs by running:
NOTE:859113.1 - How To ManuallyRemove ORACLE_OCM From Database