RMAN備份alert日志報(bào)奇怪錯(cuò)誤

布置Rman備份計(jì)劃，執(zhí)行之后發(fā)現(xiàn)alert.log中產(chǎn)生錯(cuò)誤信息：
Fri Jul  6 00:30:16 2012
Errors in file /Oracle/admin/live/udump/*****_ora_3652.trc:
Fri Jul  6 00:30:16 2012
Errors in file /Oracle/admin/live/udump/*****_ora_3652.trc:
 

Fri Jul  6 00:30:16 2012
Errors in file /Oracle/admin/live/udump/*****_ora_3652.trc
 
然后檢查備份日志，沒(méi)有發(fā)現(xiàn)錯(cuò)誤，奇怪，查看一下trace文件
[Oracle]$cat  /oracle/admin/*****/udump/*****_ora_3652.trc
/Oracle/admin/*****/udump/*****_ora_3652.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning and Data Mining options
Oracle_HOME = /oracle/product/10.2.0
System name:   Linux
Node name:     servera
Release:       2.6.9-78.ELsmp
Version:       #1 SMP Wed Jul 9 15:39:47 EDT 2008
Machine:       i686
Instance name: *****
Redo thread mounted by this instance: 1
Oracle process number: 20
Unix process pid: 3652, image:Oracle@servera(TNS V1-V3)
*** 2012-07-06 00:30:16.959
*** ACTION NAME:(0000051 STARTED16) 2012-07-06 00:30:16.958
*** MODULE NAME:(backup full datafile) 2012-07-06 00:30:16.958
*** SERVICE NAME:(SYS$USERS) 2012-07-06 00:30:16.958
*** SESSION ID:(1620.20640) 2012-07-06 00:30:16.957

metalink 解釋是一個(gè)bug 4596065，只發(fā)生在Linux X86平臺(tái)的Oracle 10.2.0.1.0下，而且只在11g里解決。這個(gè)并不是真正意義的error，可以不用管它,Just ignore it?
 
bug  4596065 信息如下
------------------------------------------------------------------------------------------
Bug No.     4596065
Filed     07-SEP-2005     Updated     18-OCT-2005
Product     Oracle Server - Enterprise Edition     Product Version     10.2.0.1.0
Platform.     Linux x86     Platform. Version     No Data
Database Version     10.2.0.1.0     Affects Platforms     Generic
Severity     Severe Loss of Service     Status     Development to Q/A
Base Bug     N/A     Fixed in Product Version     11.0

Problem statement:

RMAN BACKUP GENERATES EMPTY TRACE FILES WHEN DB_RECOVERY_FILE_DEST IS SET

 
網(wǎng)上搜索發(fā)現(xiàn)很多人亦遇到此情況
見(jiàn)鏈接 http://www.linuxidc.com/Linux/2012-07/64645.htm
有如下解釋亦可接受：
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.
 
該錯(cuò)誤信息根不必去追究和關(guān)心了，Just ignore it

本篇文章來(lái)源于 Linux公社網(wǎng)站(www.linuxidc.com)  原文鏈接：http://www.linuxidc.com/Linux/2012-07/64644.htm

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