Oracle Rman backup 產生的錯誤資訊

來源:互聯網
上載者:User

周日手工做RMAN備份的時候,在alert.log中產生了錯誤資訊。
     
Sat Jun 25 16:39:08 2012
Errors in file /home/Oracle/app/oracle/admin/XXX/udump/XXX_ora_22899.trc:
Sat Jun 25 16:39:08 2012
Errors in file /home/oracle/app/oracle/admin/XXX/udump/XXX_ora_22899.trc:
Sat Jun 25 16:39:08 2012
Errors in file /home/oracle/app/oracle/admin/XXX/udump/XXX_ora_22899.trc:

      奇怪呀,RMAN也沒有報錯資訊,趕快看看trc檔案:
     
*** 2012-06-25 16:18:53.310
*** ACTION NAME:(0000071 STARTED16) 2012-06-25 16:18:53.284
*** MODULE NAME:(backup incr datafile) 2012-06-25 16:18:53.284
*** SERVICE NAME:(SYS$USERS) 2012-06-25 16:18:53.284
*** SESSION ID:(192.52848) 2012-06-25 16:18:53.284

      沒有什麼過多的錯誤資訊顯示,基本上也是一些說明性的東西。只在metalink的forum中有這樣的提問和回答。其中一位ORACLE的support的回答比較嚴謹吧:
     
There seems to be apparently no problem with the trace file that is getting generated.

However is it the full trace file or have you just pasted the heading of the trace file.

You are correct in interpreting that this is related to the backup.

If this is not the full tracefile you can update the thread with some more information or atleast the call stack part of the trace file.

If this is the full file, then there is nothing much that can be inferred from it, and can be ignored.

      好了,這個問題可以不追究了。
      記錄一下吧。
      對一個資料的管理員來講,不要放過任何資料庫產生的資訊才對。嚴謹,是必須的。-:)

聯繫我們

該頁面正文內容均來源於網絡整理,並不代表阿里雲官方的觀點,該頁面所提到的產品和服務也與阿里云無關,如果該頁面內容對您造成了困擾,歡迎寫郵件給我們,收到郵件我們將在5個工作日內處理。

如果您發現本社區中有涉嫌抄襲的內容,歡迎發送郵件至: info-contact@alibabacloud.com 進行舉報並提供相關證據,工作人員會在 5 個工作天內聯絡您,一經查實,本站將立刻刪除涉嫌侵權內容。

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.