RMAN backup and get bad block error messages?
- From: dba1 mcc <mccdba1@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Thu, 30 Jul 2009 05:10:38 -0700 (PDT)
we have ORACLE 11G on LINUX server. We just created a new EBS system and
perform the database backup. When I do "cold backup" and "hot backup", there is
NO error. While I perform RMAN backup and I got error messages:
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/29/2009
20:38:42
ORA-19566: exceeded limit of 0 corrupt blocks for file
/u/EBS/EBSDB01/db/apps_st/data/system04.dbf
Alter.log also have messages:
Hex dump of (file 352, block 165656) in trace file
/u/EBS/EBSDB01/db/tech_st/11.1.0/admin/XXX/diag/rdbms/ebsdb01/EBSDB01/trace/EBSDB01_ora_6824.trc
Corrupt block relative dba: 0x58028718 (file 352, block 165656)
Completely zero block found during backing up datafile
Reread of blocknum=165656, file=/u/EBS/EBSDB01/db/apps_st/data/system04.dbf.
found same corrupt data
My question are:
1. Why "cold backup" and "hot backup" Not complain, but RMAN complain?
2. how to fix this bad block without lost data?
Thanks.
--
http://www.freelists.org/webpage/oracle-l
Other related posts: