今天做logmnr时, execute dbms_logmnr_d.set_tablespace('ts_strmrep');
没有重新指回到sysaux,导致报错。
alert日志中,不断报错:
Tue Jun 16 12:18:25 2015
Errors in file /u02/app/oracle/diag/rdbms/uenpay/UENPAY/trace/UENPAY_cjq0_14287.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors
今天给Streams管理用户授权时遇到如下错误:
SQL> exec DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE(grantee => 'strmrep',grant_privileges => true);
BEGIN DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE(grantee => 'strmrep',grant_privileges => true); END;
*
ERROR at line 1:
ORA-04063: package body "SYS.DBMS_LOGREP_UTIL" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_LOGREP_UTIL"
ORA-06512: at "SYS.DBMS_STREAMS_AUTH", line 1211
ORA-06512: at line 1
查询Streams不支持对象视图也是有错误:
SQL> select * from DBA_STREAMS_UNSUPPORTED;
select * from DBA_STREAMS_UNSUPPORTED
*
ERROR at line 1:
ORA-04063: package body "SYS.DBMS_LOGREP_UTIL" has errors
后来想起是由于原先做过 execute dbms_logmnr_d.set_tablespace('ts_strmrep'); 操作把logminer相关对象从sysaux表空间迁移到ts_strmrep了,清除Streams配置的时候, 也把表空间ts_strmrep给drop了, 造成logminer相关对象都没了.
从metalink找到重建方法:
$ sqlplus / as sysdba
SQL> @?/rdbms/admin/dbmslmd.sql
SQL> @?/rdbms/admin/prvtlmd.plb
SQL> @?/rdbms/admin/utlrp.sql
为防止下次再犯错, 还是把logminer相关对象放回sysaux表空间, 因为建库时把sysaux表空间设置成了自动扩展, 所以不怕被logminer的日志撑爆了.
SQL> execute dbms_logmnr_d.set_tablespace('sysaux');
--END--
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/28194062/viewspace-1701086/
,如需转载,请注明出处,否则将追究法律责任。