RMAN, v$session_longops and Ora-03113
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10006: error running sql statement: select sofar, context from v$session_longops where sid = (select distinct sid from v$mystat) and opname like 'RMAN:%' order by start_time desc, context desc
RMAN-10002: ORACLE error: ORA-03113: end-of-file on communication channel
經查﹐發現是由X$KSULOP系統表所引起的﹐也就是我在查詢 X$KSULOP時也會出ora-03113
SQL> select count(*) from X$KSULOP;
select count(*) from X$KSULOP
*
ERROR 在行 1:
ORA-03113: 通訊通道上出現 EOF
metalink上的答案是:Shutdown and restart the target instance
RMAN uses v$session_longops to record it's progress. After each backup set it uses the DBMS package to update "progress" in the V$ view, having first queried out of the view to find some relevant data within . So when the view goes "bad" RMAN does its initial backup set/piece, trys to update v$session_longops and subsequently gets an Ora-03113 error and dies. Hence, the backup "fails" inasmuch as it did not run to completion. I reality we get less than 10% of our Db backed-up when this problem is in force
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/33600/viewspace-266401/ ，如需转载，请注明出处，否则将追究法律责任。
