ALERT日志中报错如下:
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
数据库版本:
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
#################
参考MOS文档:
"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)
报错原因是:
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. ---目录不存在
ORACLE_OCM 账户是用来管理Oracle Configuration Manager的。 默认情况下, 该账户是Expired and locked状态。
该错误只出现在OracleRDBMS 11.2.0.3 的版本(新安装的db,或者从其他版本升级到11.2.0.3的),或者Oracle Configuration Manager 的版本大于10.3.3.0.0。
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.
如果不需要向MOS上传搜集信息,可以删除用户ORACLE_OCM来解决,语句:
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.
#####################################
如是10g--Version 10.2.3 to 10.3.1,参考MOS文档:How To Manually Remove ORACLE_OCM From Database (文档 ID 859113.1)
解决方法:
如不需要使用此功能,可以删除用户ORACLE_OCMT和相应DIRECTORY来解决,语句:
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;
- 大小: 44.2 KB
分享到:
相关推荐
oracle19c缺少的函数
-- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... -- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... -- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... ...
ora-01033:oracle initialization or shutdown in progress 解决方法 ora-01033:oracle initialization or shutdown in progress 解决方法 ora-01033:oracle initialization or shutdown in progress 解决方法 ora-...
调整参数后引起,ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at least 3 2768M 的解决方案
ORA-00904 WMSYS.WM_CONCAT标识符无效解决方案
在运行查询SELECT * FROM V$SESSION 会出现ORA-29275:部分多字节字符的错误,这是什么原因开始我不得其解,网上也没有介绍什么好办法。本文给出答案。
ORA-03113 "end_of_file on communication channel" ORA-03113 "end_of_file on communication channel" ORA-03113 "end_of_file on communication channel
ORA-01036:非法的变量名/编号 oracle特有的错误
SQL>alter system set control_files=’/u01/app/oracle/oradata/prod/ora_control1.ctl’,’/u01/app/oracle/oradata/prod/ora_control2.ctl’ scope=spfile; 解决方法: 1.show parameter spfile; 这时候可以...
ORA-12154: TNS: 无法解析指定的连接标识符的解决方法
ORA-00031:标记要终止的会话解决方案; ORA-00031:标记要终止的会话解决方案;
oracle报错ora-12541:TNS无监听程序
NULL 博文链接:https://3w1h.iteye.com/blog/1211779
ORA-00603: ORACLE server session terminated by fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:sskgxp_select failed with status: 3 ORA-27301: OS ...
Oracle 回收站功能,彻底删除表ORA-00933:SQL command not properly ended,由于删除触发器引起的。数据交换不能再建触发器。
错误描述:oracle远程连接服务器出现 ORA-12170 TNS:连接超时 错误检查:有很多是oracle自身安装的问题,但是我这里服务器配置正常,监听正常,服务正常,远程可以ping通服务器。 这里主要是防火墙问题,解决办法: ...
oracle 12 c ORA-01017: 用户名/口令无效; 登录被拒绝
最近在工作中遇到了一个问题,错误是Oracle dbca时报错:ORA-12547: TNS:lost contact,通过查找相关的资料终于找到了解决的方法,下面分享给大家,话不多说了,来一起看看详细的介绍吧。 环境: OS:RHEL6.5 x86-...
Oracle新手使用常见错误小集,1、ORA-12541:TNS:没有监听器。2、ORA-12500:TNS:监听程序无法启动专用服务器进程或ORA-12560:TNS:协议适配器错误。 3、如果数据库服务启动失败,则很有可能是其注册表项值损坏。。。4...