RE: RMAN backup and get bad block error messages?
- From: "Crisler, Jon" <Jon.Crisler@xxxxxxx>
- To: <mccdba1@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 30 Jul 2009 11:52:44 -0400
You should now run a test to determine how much damage this file has
sustained. If its just one bad block, and it appears empty, then the
damage is minimal. Because you have a RMAN setting (probably default)
that says "stop after 1 bad block" you do not know the scope of the
damage.
Your first step is Metalink technote 28814.1 and also 283053.1
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of dba1 mcc
Sent: Thursday, July 30, 2009 8:11 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RMAN backup and get bad block error messages?
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/tr
ace/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.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
