ORA-12012: error on auto execute of job "ORACLE_OCM"."MGMT_CONFIG_JOB_2_1"

Wed Jan 14 22:00:01 2015
Errors in file /s01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_j000_43937.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
Thu Jan 15 01:52:44 2015
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Thu Jan 15 06:51:10 2015
Thread 1 advanced to log sequence 625 (LGWR switch)
  Current log# 1 seq# 625 mem# 0: +DATA/orcl/onlinelog/group_1.262.854191287
  Current log# 1 seq# 625 mem# 1: +FRA/orcl/onlinelog/group_1.257.854191289
Thu Jan 15 06:51:12 2015
Archived Log entry 1709 added for thread 1 sequence 624 ID 0x525ead30 dest 1:
Thu Jan 15 21:52:43 2015
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Thu Jan 15 21:52:43 2015
Starting background process VKRM
Thu Jan 15 21:52:43 2015
VKRM started with pid=40, OS id=3234
Thu Jan 15 21:53:26 2015
Thread 1 advanced to log sequence 626 (LGWR switch)
  Current log# 2 seq# 626 mem# 0: +DATA/orcl/onlinelog/group_2.261.854191289
  Current log# 2 seq# 626 mem# 1: +FRA/orcl/onlinelog/group_2.258.854191293
Thu Jan 15 21:53:27 2015
Archived Log entry 1713 added for thread 1 sequence 625 ID 0x525ead30 dest 1:
Thu Jan 15 22:00:03 2015
Errors in file /s01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_j000_3392.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
Fri Jan 16 01:52:42 2015
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Fri Jan 16 17:53:27 2015
Thread 1 advanced to log sequence 627 (LGWR switch)
  Current log# 5 seq# 627 mem# 0: +DATA/orcl/onlinelog/group_5.265.854191293
  Current log# 5 seq# 627 mem# 1: +FRA/orcl/onlinelog/group_5.259.854191295
Fri Jan 16 17:53:29 2015
Archived Log entry 1717 added for thread 1 sequence 626 ID 0x525ead30 dest 1:
Fri Jan 16 21:52:42 2015
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Fri Jan 16 21:52:42 2015
Starting background process VKRM
Fri Jan 16 21:52:42 2015
VKRM started with pid=41, OS id=44218
Fri Jan 16 22:00:01 2015
Errors in file /s01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_j002_44371.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
Sat Jan 17 01:52:42 2015

The error is reported every 24 hours in the alertLog file of a 11.2.0.3 database:

SQL*Plus: Release 11.2.0.3.0 Production on Wed Jan 28 11:07:18 2015

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

SQL> connect / as sysdba
Connected.
SQL> select JOB_NAME,STate from ALL_SCHEDULER_JOBS where owner='ORACLE_OCM';

JOB_NAME                       STATE
------------------------------ ---------------
MGMT_CONFIG_JOB                SCHEDULED
MGMT_STATS_CONFIG_JOB          SCHEDULED

SQL> select * from dba_directories where DIRECTORY_NAME like '%OCM_CONFIG%';

OWNER                          DIRECTORY_NAME
------------------------------ ------------------------------
DIRECTORY_PATH
--------------------------------------------------------------------------------
SYS                            ORACLE_OCM_CONFIG_DIR
/s01/app/oracle/product/11.2.0/dbhome_1/ccr/state

SQL>

錯誤原因
Newer database releases are automatically instrumented for OCM collections. But here, the OCM instrumentation job is trying to write to a "state" directory which doesn't yet exists.
MGMT_DB_LL_METRICS wants to write to ORACLE_OCM_CONFIG_DIR2, which is not created by the built-in instrumentation scripts.
 
 
處理辦法
Problem is fixed with OCM Collector version 10.3.7
 
A. But out-of-box the 11.2 database includes earlier OCM version, therefore one must re-configure database for OCM collections by running the "ORACLE_HOME/ccr/admin/scripts/installCCRSQL" script. If script is missing, first configure OCM by running "ORACLE_HOME/ccr/bin/setupCCR".
Pay attention when on RAC database, with a non-shared file system environment, must set the ORACLE_CONFIG_HOME environment variable to $ORACLE_HOME prior to running the installCCRSQL.sh script. Reference: Oracle Configuration Manager Installation and Administration Guide
 
or
 
B. when not using the OCM Collector, remove the OCM objects from database:
SQL> drop user ORACLE_OCM cascade;
OCM is a standalone, separate tool and removing won't affect the database functionality.
 
Or could simply disable the OCM jobs by running:
 
exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB');
exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');