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

1: 버전 정보
운영 체제 버전: AIX 61009
데이터베이스 버전: 11.2.0.3.11(RAC)
 
2: 오류 설명
데이터베이스의 alert 로그에서 다음과 같은 오류가 발견되었습니다.

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
Tue Oct 21 22:13:51 2014

 
3. 오류 원인 및 해결 방안
OS에서 1453959.1 이 노트의 상세한 내용은 다음과 같다.

"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



Symptoms



Changes



Cause



Solution



References


--------------------------------------------------------------------------------



 Applies to: 
Oracle Configuration Manager - Version 10.3.3.0.0 and later
 Information  in this document applies to any platform.

Symptoms 

Following error is reported every 24 hours in the alertLog file of a 11.2.0.3 database:
 
Errors in 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

Changes 

Newly installed 11.2.0.3 database, or recently upgraded to 11.2.0.3 from an earlier release. 

Cause 

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.
<span style="color:#ff0000;">## OCM , .
</span>To verify the OCM db directories, run as sysdba:
 SQL>select * from dba_directories where DIRECTORY_NAME like '%OCM_CONFIG%';
 
MGMT_DB_LL_METRICS wants to write to ORACLE_OCM_CONFIG_DIR2, which is not created by the built-in instrumentation scripts. 
<span style="color:#ff0000;">##MGMT_DB_LL_METRICS ORACLE_OCM_CONFIG_DIR2 ， .</span>
Solution 

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') 

References 

NOTE:859113.1 - How To Manually Remove ORACLE_OCM From Database

##MOS에는 다음과 같은 세 가지 해결 방법이 있습니다.
1. OCM 재구성
2. OCM Collector를 사용하지 않아도 OCM 사용자 및 관련 객체를 삭제할 수 있습니다.
3. OCMjob 비활성화
 
##MOS에서 버그 "Bug 13385346: GCR0 TRACE FILES CONTINUOUSLY CREATED WITH KJGCR_DELETESO MESSAGES"로 나열된 임시 해결 방안은 버그 보고를 무시하는 것입니다. 버그는 12.1에서 복구되었습니다.