OCM is the Oracle Configuration Manager, a tool to proactively monitor your Oracle environment to provide this information to Oracle Software Support. As OCM is installed by default in many databases but is some sort of independent from the database’s version you won’t expect any issues during or after a database upgrade 😉
But after the upgrade from Oracle 188.8.131.52 to Oracle 184.108.40.206 on Exadata X2-2 one of my customers found the following error in the alert.log every 24 hours:
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
Why is that happening and how to solve that issue now?
OCM is trying to write to a local directory which does not exist. Besides that the OCM version delivered with Oracle Database Patch Set 220.127.116.11 is older than the newest available OCM Collector 10.3.7 – the one which has that issue fixed.
So you’ll either drop OCM completely if you won’t use it:
SQL> drop user ORACLE_OCM cascade;
or you’ll disable the collector jobs:
SQL> exec dbms_scheduler.disable(‘ORACLE_OCM.MGMT_CONFIG_JOB’);
SQL> exec dbms_scheduler.disable(‘ORACLE_OCM.MGMT_STATS_CONFIG_JOB’);
or you’ll have to reconfigure OCM – and please see MOS Note:1453959.1 for a detailed description how to do that – it’s basically executing the script ORACLE_HOME/ccr/admin/scripts/installCCRSQL – but there maybe other things to consider especially in a RAC environment.
Just for the records: Bug 12927935: ORA-12012, ORACLE_OCM.MGMT_DB_LL_METRICS, ORA-29280