Oracle 11.2.0.3 RAC環境--ORA-12012 ,ORA-2928 錯誤處理

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.
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.

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')
--------------------------------------------------------------
這個問題在升級之前的11.2.0.2版本上沒有出現過，顯然這是升級到11.2.0.3帶來的bug。而報錯的JOB所屬使用者


ORACLE_OCM是Oracle配置管理的專屬使用者。根據文件"ORA-12012: error on auto execute of job 
ORACLE_OCM.MGMT_CONFIG_JOB_2_1" And "ORA-29280: invalid directory path" In Database AlertLog [ID 1453959.1]
，導致問題的原因是資料庫升級到11.2.0.3後，Oracle會啟用自動OCM collection，在這個過程中Oracle嘗試使用目錄
ORACLE_OCM_CONFIG_DIR2，但這個目錄在建立過程中並未建立。
解決該問題並不複雜，對於不需要使用配置管理器的使用者而言，可以簡單的DISABLE掉這個JOB，或者直接將ORACLE_OCM用
戶刪除：
exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB')
exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB')
如果需要使用配置管理器，可以透過ORACLE_HOME/ccr/admin/scripts/installCCRSQL指令碼來重新設定配置管理器。如果上
面的指令碼缺失，可以透過先執行ORACLE_HOME/ccr/bin/setupCCR指令碼的方式來進行配置。