Oracle Rman backup 產(chǎn)生的錯(cuò)誤信息

周日手工做RMAN備份的時(shí)候，在alert.log中產(chǎn)生了錯(cuò)誤信息。
     
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也沒(méi)有報(bào)錯(cuò)信息，趕快看看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

      沒(méi)有什么過(guò)多的錯(cuò)誤信息顯示，基本上也是一些說(shuō)明性的東西。只在metalink的forum中有這樣的提問(wèn)和回答。其中一位Oracle的support的回答比較嚴(yán)謹(jǐn)吧：
     
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.

服務(wù)器租用/服務(wù)器托管中國(guó)五強(qiáng)！虛擬主機(jī)域名注冊(cè)頂級(jí)提供商！15年品質(zhì)保障！--億恩科技[ENKJ.COM]