RE: checking for block corruption
Date: Mon, 21 May 2012 15:33:12 -0400
Message-ID: <6AFC12B9BFCDEA45B7274C534738067F925D4617_at_AAPQMAILBX02V.proque.st>
Ok, first, 'BACKUP VALIDATE' will *not* actually do a backup: http://docs.oracle.com/cd/B19306_01/backup.102/b14193/toc.htm#sthref34
Based on the error you're seeing, you need to put the backup copy into archivelog mode, to be able to successfully do the test.
Finally, see here:
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmconc1.htm#BRADV115
for details of options that should and should not be set for a full validation.
Hope that helps,
-Mark
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Dba DBA
Sent: Monday, May 21, 2012 2:43 PM
To: ORACLE-L
Subject: checking for block corruption
I need to run a block corruption test. I have a BCV copy of prod I am running this on. We are not using RMAN for prod backups. I can't change this.
DB Version: 10.2.0.5.6
DB Size: 10 TBs
files are on raw partitions
rman target /
backup validate database;
if I run this will this actually backup the DB? When I read the docs they seemed to say it would only do a validate check. We have the DB copy in noarchivelog mode. When I ran that command I get:
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/21/2012
16:05:09
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
If backup validate only checks for block corruption why does it care if I am in archivelog mode ( i know i can bounce the db or turn it off. I want to make sure I'm not actually taking a backup).
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Mon May 21 2012 - 14:33:12 CDT