How to solve the ORA-12012 error

The error in the alert log is as follows:

Sun Mar 30 06:05:40 2014

Errors in FILE/ORACLE/APP/ORACLE/DIAG/RDBMS/ZSCIMS/ZSCIMS1/TRACE/ZSCIMS1_J001_15269946.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

Database version:

Oracle Database 11g Enterprise Edition release 11.2.0.3.0-64bit Production

Pl/sql Release 11.2.0.3.0-production

CORE 11.2.0.3.0 Production

TNS for Ibm/aix RISC system/6000:version 11.2.0.3.0-production

Nlsrtl Version 11.2.0.3.0-production

#################

Refer to MOS Documentation:

"Ora-12012:error on Auto execute of Job oracle_ocm. Mgmt_config_job_2_1 "and" Ora-29280:invalid directory path in Database alertlog (document ID 1453959.1)

The reason for the error is:

Newer database releases are automatically instrumented for OCM collections.   But here, the OCM instrumentation job are trying to write to a "state" directory which doesn ' t yet exists. ---directory does not exist

The ORACLE_OCM account is used to manage Oracle Configuration Manager. By default, the account is the expired and locked state.

This error only occurs in the version of Oraclerdbms 11.2.0.3 (newly installed DB, or upgraded from another version to 11.2.0.3), or the version of Oracle Configuration Manager is greater than 10.3.3.0.0.

To verify the OCM DB directories, run as SYSDBA:---can confirm that the following directory does not exist by using the following statement

Sql>select * from dba_directories where directory_name like '%ocm_config% ';

Mgmt_db_ll_metrics wants to write to ORACLE_OCM_CONFIG_DIR2, which are not created by the built-in instrumentation.

If you do not need to upload information to MOS, you can delete the user oracle_ocm to resolve the statement:

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.

#####################################

If 10g--version 10.2.3 to 10.3.1, refer to MOS documentation: How to Manually Remove oracle_ocm from Database (document ID 859113.1)

Workaround:

If you do not need to use this feature, you can delete the user oracle_ocmt and corresponding directory to resolve the statement:

In order to manually remove the ORACLE_OCM user and associated objects from database, run:

sql> drop user oracle_ocm cascade;

sql> Drop directory Oracle_ocm_config_dir;

This column more highlights: http://www.bianceng.cnhttp://www.bianceng.cn/database/Oracle/