Backup validate command

I have few questions to clear my confusion.Can anyone please clarify it.
1)Does Backup validate check logical database plus archivelog all takes same time as real backup?
2)does database needs to be in archivelog mode?
3)can this validate command run mount state?
Thanks

Here is a simple illustration for you;
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
Starting backup at 17-AUG-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00002 name=/db/OPTIMA/oradata/opttest/opttest/UNDOTBS1.dbf
input datafile fno=00341 name=/db/OPTIMA/oradata/opttest/data/NORS_OWCTTS_D_02.dbf
input datafile fno=00369 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_GROUP_D_03.dbf
input datafile fno=00307 name=/db/OPTIMA/oradata/opttest/data/NORS_TONES_D_02.dbf
input datafile fno=00311 name=/db/OPTIMA/oradata/opttest/data/NORS_SINGLE_UNIT_PM_D_02.dbf
input datafile fno=00313 name=/db/OPTIMA/oradata/opttest/data/NORS_PM_D_02.dbf
input datafile fno=00318 name=/db/OPTIMA/oradata/opttest/data/NORS_RTLTSUM_D_02.dbf
input datafile fno=00319 name=/db/OPTIMA/oradata/opttest/data/NORS_SOTS_D_02.dbf
input datafile fno=00320 name=/db/OPTIMA/oradata/opttest/data/NORS_SYSPERF_D_02.dbf
input datafile fno=00328 name=/db/OPTIMA/oradata/opttest/data/NORS_TREATMENT_D_02.dbf
input datafile fno=00329 name=/db/OPTIMA/oradata/opttest/data/NORS_TRUNK_MODULES_D_02.dbf
input datafile fno=00123 name=/db/OPTIMA/oradata/opttest/data/NORS_SINGLE_UNIT_PM_D_01.dbf
input datafile fno=00129 name=/db/OPTIMA/oradata/opttest/data/NORS_TONES_D_01.dbf
input datafile fno=00147 name=/db/OPTIMA/oradata/opttest/data/NORS_C7LKSET_D_01.dbf
input datafile fno=00149 name=/db/OPTIMA/oradata/opttest/data/NORS_C7MTP_D_01.dbf
input datafile fno=00151 name=/db/OPTIMA/oradata/opttest/data/NORS_C7ROUTE_D_01.dbf
input datafile fno=00155 name=/db/OPTIMA/oradata/opttest/data/NORS_CALL_CONTROL_D_01.dbf
input datafile fno=00157 name=/db/OPTIMA/oradata/opttest/data/NORS_CDIVGRP_D_01.dbf
input datafile fno=00159 name=/db/OPTIMA/oradata/opttest/data/NORS_COMPUTING_MODULE_D_01.dbf
input datafile fno=00163 name=/db/OPTIMA/oradata/opttest/data/NORS_DTSRPM_D_01.dbf
input datafile fno=00165 name=/db/OPTIMA/oradata/opttest/data/NORS_EXND_CALL_CONTROL_D_01.dbf
input datafile fno=00167 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_GROUP_D_01.dbf
input datafile fno=00169 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_STATS_D_01.dbf
input datafile fno=00171 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_TRAFFIC_D_01.dbf
input datafile fno=00173 name=/db/OPTIMA/oradata/opttest/data/NORS_IWUCGRP_D_01.dbf
input datafile fno=00179 name=/db/OPTIMA/oradata/opttest/data/NORS_MPCLINK3_D_01.dbf
input datafile fno=00183 name=/db/OPTIMA/oradata/opttest/data/NORS_OFFICE_TRAFFIC_ROUT_D_01.dbf
input datafile fno=00185 name=/db/OPTIMA/oradata/opttest/data/NORS_OWCTTS_D_01.dbf
input datafile fno=00349 name=/db/OPTIMA/oradata/opttest/data/NORS_LINE_ACCESS_D_02.dbf
input datafile fno=00011 name=/db/OPTIMA/oradata/opttest/opttest/OPTIMA_ALARMS_I.dbf
input datafile fno=00012 name=/db/OPTIMA/oradata/opttest/opttest/SAMPLE_VENDORD.dbf
input datafile fno=00013 name=/db/OPTIMA/oradata/opttest/opttest/SAMPLE_VENDORI.dbf
input datafile fno=00110 name=/db/OPTIMA/oradata/opttest/system/DEF_NORTEL_SWITCHING_S_01.dbf
input datafile fno=00115 name=/db/OPTIMA/oradata/opttest/data/NORS_PM_D_01.dbf
input datafile fno=00177 name=/db/OPTIMA/oradata/opttest/data/NORS_LINE_TRAFFIC_D_01.dbf
input datafile fno=00347 name=/db/OPTIMA/oradata/opttest/data/NORS_MPCLINK3_D_03.dbf
input datafile fno=00350 name=/db/OPTIMA/oradata/opttest/data/NORS_EXND_CALL_CONTROL_D_03.dbf
input datafile fno=00351 name=/db/OPTIMA/oradata/opttest/data/NORS_OWCTTS_D_03.dbf
input datafile fno=00354 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_STATS_D_03.dbf
input datafile fno=00355 name=/db/OPTIMA/oradata/opttest/data/NORS_SYSPERF_D_03.dbf
input datafile fno=00357 name=/db/OPTIMA/oradata/opttest/data/NORS_TRUNK_MODULES_D_03.dbf
input datafile fno=00358 name=/db/OPTIMA/oradata/opttest/data/NORS_TREATMENT_D_03.dbf
input datafile fno=00359 name=/db/OPTIMA/oradata/opttest/data/NORS_SOTS_D_03.dbf
input datafile fno=00360 name=/db/OPTIMA/oradata/opttest/data/NORS_RTLTSUM_D_03.dbf
input datafile fno=00362 name=/db/OPTIMA/oradata/opttest/data/NORS_OFFICE_TRAFFIC_ROUT_D_03.dbf
input datafile fno=00363 name=/db/OPTIMA/oradata/opttest/data/NORS_C7ROUTE_D_03.dbf
input datafile fno=00365 name=/db/OPTIMA/oradata/opttest/data/NORS_CDIVGRP_D_03.dbf
input datafile fno=00368 name=/db/OPTIMA/oradata/opttest/data/NORS_CALL_CONTROL_D_03.dbf
input datafile fno=00370 name=/db/OPTIMA/oradata/opttest/data/NORS_COMPUTING_MODULE_D_03.dbf
input datafile fno=00371 name=/db/OPTIMA/oradata/opttest/data/NORS_C7MTP_D_03.dbf
input datafile fno=00372 name=/db/OPTIMA/oradata/opttest/data/NORS_IWUCGRP_D_03.dbf
input datafile fno=00376 name=/db/OPTIMA/oradata/opttest/data/NORS_C7LKSET_D_03.dbf
input datafile fno=00377 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_TRAFFIC_D_03.dbf
input datafile fno=00378 name=/db/OPTIMA/oradata/opttest/data/NORS_DTSRPM_D_03.dbf
input datafile fno=00352 name=/db/OPTIMA/oradata/opttest/data/NORS_ANN_D_03.dbf
user interrupt received
Finished backup at 17-AUG-10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03099: job cancelled at user request
RMAN> --> It was validating with the archivelog mode
RMAN> exit
Recovery Manager complete.
$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Aug 17 16:29:12 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1375731712 bytes
Fixed Size                  2056088 bytes
Variable Size             704643176 bytes
Database Buffers          654311424 bytes
Redo Buffers               14721024 bytes
Database mounted.
SQL> alter database noarchivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> exit;
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
$ rman target /
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Aug 17 16:30:00 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: OPTTEST (DBID=750193206)
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
Starting backup at 17-AUG-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1461 devtype=DISK
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:07
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:08
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:09
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:09
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:10
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:11
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:11
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:12
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:13
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:13
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:14
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:15
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:15
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:16
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:17
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=297 recid=7633 stamp=727146412
input archive log thread=1 sequence=298 recid=7634 stamp=727221971
input archive log thread=1 sequence=299 recid=7635 stamp=727222952
input archive log thread=1 sequence=300 recid=7636 stamp=727281385Regards.
Ogan

Similar Messages

Question on backup validate datafile command

DB Version: 10gR2, 11GR2
Is the following command meant to check block corruption in the original datafile or is it meant to check if the rman backup of this file is fit for restore?
backup validate datafile 1;The equivalent of the above command in 11g is
validate datafile 1;Right?

Both are true.
The VALIDATE command is to check for corrupt blocks and missing files, or to determine whether a backup set can be restored.
If the backup validation discovers corrupt blocks, then RMAN updates the V$DATABASE_BLOCK_CORRUPTION view with rows describing the corruptions. After a corrupt block is repaired, the row identifying this block is deleted from the view.
Oracle 11g,
The options in the VALIDATE command are semantically equivalent to options in the BACKUP VALIDATE command.
refer,
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsynta053.htm
Thanks

BACKUP VALIDATE vs VALIDATE in checking logical/physical corruption

Hello all,
I am checking if our 10gR2 database has any physical or logical corruption. I have read in some places where they state that VALIDATE command is enough to check database for physical corruption. Our database was never backed up by RMAN specifically before. Are any configuration settings needed for running BACKUP VALIDATE command? The reason I am asking is because just the VALIDATE command returns an error and BACKUP VALIDATE command runs without error but it is not showing the
"File Status Marked Corrupt Empty Blocks Blocks Examined High SCN" lines.
I used the command in two different formats and both do not show individual data file statuses:
RMAN> run {
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE DEVICE TYPE DISK PARALLELISM 10 BACKUP TYPE TO BACKUPSET;
BACKUP VALIDATE CHECK LOGICAL DATABASE FILESPERSET=10;
RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE
RMAN> VALIDATE DATABASE;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "database": expecting one of: "backupset"
RMAN-01007: at line 1 column 10 file: standard input
However on a different database already being backed up by RMAN daily, BACKUP VALIDATE output shows list of datafiles and STATUS = OK as below:
List of Datafiles
=================
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
How can we check every individual datafile status. Appreciate your responses. Thanks.

Hi,
After you have run:
BACKUP VALIDATE CHECK LOGICAL DATABASE You can use sqlplus and run:
select * from v$database_block_corruption.The output will tell you which block in which datafile is corrupt.
Regards,
Tycho
Edited by: tychos on 8-sep-2011 18:34

Backup validate check logical database

What is exactly the following RMAN command do? I want to know Is it doing a full backup or not?
rman> backup validate check logical database' . Kindly help me.

RMAN does not physically backup the database with this command. But it reads all blocks and checks for corruptions.
If it finds corrupted blocks it will place the information about the corruption into a view:
v$database_block_corruption;
Now we can tell RMAN to recover all the blocks which it has found as being corrupt:
RMAN> blockrecover corruption list; # (all blocks from v$database_block_corruption)
Use below link for reference.
http://luhartma.blogspot.com/2006/04/how-to-check-for-and-repair-block.html
-Bharath

Validate command syntax

Hello,
I need to validate if a database has been backed up succesfully so I want to execute rman validates command.
I checked oracle manuals and I found validates command is a parameter of restore command:
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10770/rcmsynta65.htm#86797
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10770/rcmsynta51.htm#85191
I already duplicated databases using rman, but I'm not sure about syntax for validating. Is the following code right if I want just to validate database backup?
rman rcvcat rman/rman@rman target sys/password@database auxiliary / cmdfile /home/oracle/restore_dup.sh
Where restore_dup.sh is:
run {
allocate auxiliary channel 'dev_0' type 'sbt_tape';
allocate auxiliary channel 'dev_1' type 'sbt_tape';
allocate auxiliary channel 'dev_2' type 'sbt_tape';
allocate auxiliary channel 'dev_3' type 'sbt_tape';
restore target database validates;
Note that...
- OS is HP-UX 11.00
- Database is Oracle 8.1.7
- I CANNOT recover anything as database I want to validate is a production environment.
Thanks in advance for your help.
Regards,
Carles

I never worked with RMAN 8.1.7 (only newer versions)
According the documentation you can validate only a backupset in RMAN 8.1.7:
- validate backupset <bs_number>;
http://download-east.oracle.com/docs/cd/A87860_01/doc/server.817/a76990/rmansy50.htm#6148
http://download-east.oracle.com/docs/cd/A87860_01/doc/server.817/a76990/preparer.htm#435378
The validation for the full DB in a new feature in RMAN 9i.
Bye, Aron

Backup validate :Error

Hi Expert,
while executing backup validate database archivelog all in one of the server i received this
RMAN> backup validate database archivelog all;
Starting backup at 04-JUL-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=18 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/04/2007 06:21:34
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specificati
on does not match any archive log in the recovery catalog
What this means and is it any major concern?
Thanks
Shaan

this means you didn't have any archives and rman is unable to validate them.
RMAN does not actually produce backup sets, but rather reads the specified files in their entirety, to determine whether they can be backed up and are not corrupted.
found at:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmbackp008.htm#sthref672

Backup validate check logical

hi,
An mssql dba asked me if oracle could do logical/physical corruption checking when performing backups. Im aware of BACKUP VALIDATE CHECK LOGICAL.
However, it doesn't create any backup. It just checks for corruption. If I remember, you can run BACKUP CHECK LOGICAL which will actually create the backup and check logical at the same time, but my question is...
Why would you not want one or both of these as standard? I get it that there's overhead, more so for VALIDATE, but would you really want backups that contain corruption? Even if you keep 30 days worth of backups, you could realise after 40 days that you had corruption, and not be able to restore.
Or is the reasoning behind not making it default, that you've got 'enough' backups that even if a datafile gets logical/physical corruption, you're bound to discover it before your backups become obsolete, and that it's then not worth the overhead of making it default?

You can have the settings with SET MAXCORRUPT FOR DATAFILE.
By default a checksum is calculated for every block read from a datafile and stored in the backup or image copy. If you use the NOCHECKSUM option, then checksums are not calculated. If the block already contains a checksum, however, then the checksum is validated and stored in the backup. If the validation fails, then the block is marked corrupt in the backup.
The SET MAXCORRUPT FOR DATAFILE command sets how many corrupt blocks in a datafile that BACKUP will tolerate. If a datafile has more corrupt blocks than specified by the MAXCORRUPT parameter, the command terminates. If you specify the CHECK LOGICAL option, RMAN checks for logical and physical corruption.
By default, the BACKUP command terminates when it cannot access a datafile. You can specify parameters to prevent termination, as listed in the following table.
If you specify the option ... Then RMAN skips...
SKIP INACCESSIBLE Inaccessible datafiles. A datafile is only considered inaccessible if it cannot be read. Some offline datafiles can still be read because they exist on disk. Others have been deleted or moved and so cannot be read, making them inaccessible.
SKIP OFFLINE Offline datafiles.
SKIP READONLY Datafiles in read-only tablespaces.

Restore Validate Database vs Backup Validate Database

Hi,
I want to add the following sentence after taking the backup using following command (backup as compressed backupset database plus archivelog;)
restore database validate;
or
backup validate database;
which one is best?

It depends on what you are trying to accomplish, as per documentation:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#sthref141BACKUP .. VALIDATE: Causes RMAN to scan the specified files and verify their contents, testing whether this file can be backed up. RMAN creates no output files. Use this command periodically to check for physical and logical errors in database files.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta051.htm#sthref796
RESTORE... VALIDATE causes RMAN to select existing backups that it would use to perform a RESTORE operation, and scan them all to ensure that they are present and free of corruption.>
Guessing what you're trying to do, I recommend:
backup check logical as compressed backupset database plus archivelog;
restore validate database;
CHECK LOGICAL. Tests data and index blocks that pass physical corruption checks for logical corruption, for example, corruption of a row piece or index entry. If RMAN finds logical corruption, then it logs the block in the alert.log and server session trace file. HTH
Enrique
PS If you have access to Metalink see Note:388422.1 Top 10 Backup and Recovery best practices.
Edited by: Enrique Orbegozo on Dec 17, 2008 4:21 PM

Restore database validate command

Hey Guys..
Is there a way to attempt to run the "restore database validate" command specifying a different location for the backup?
Lets say i have a backup in the following location: C:\SimpleBackup
How can i run the restore validate command to that location instead of the default flash recovery?

We always use the :
set newname for datafile 1 to '/opt/dbsid/db01/system.dbf';
set newname for datafil 2 to '/opt/dbsid/db01/temp01.dbf';
to restore backup files to another location.
Is that useable here ?
Edit: I just re-read the question. Is the c:\simplebackup a destination to put restored files to, or is it the location of the rman archive ?
if the first is true, then the above can't be used.
Edited by: orafrf on Mar 16, 2009 4:37 PM

PERFORMING A TEST BACKUP (VALIDATE BACKUP) USING RMAN

제품 : RMAN
작성날짜 : 2002-05-30
PERFORMING A TEST BACKUP (VALIDATE BACKUP) USING RMAN
=====================================================
PURPOSE
RMAN을 이용하여 Test Backup을 수행하기 위한 정보를 제공한다.
EXPLANATION
8.1.7 부터 RMAN에서 BACKUP command에 VALIDATE keyword를 사용할 수 있게 되었다
이 명령의 수행은 다음과 같은 작업을 수행한다.
- Datafile의 physical and logical corruption을 check한다.
- 모든 database file들이 존재하는지, 그리고 올바른 위치에 있는지를 검증한다.
RMAN은 실제적으로 backupset을 생성하지 않는다 그러나 그것들이 backup될 수
있는지 없는지를 결정하기 위해서 기술된 file들을 scan한다.
BACKUP VALIDATE 는 backup job을 수행시 수행되는 것을 제외하고는
RESTORE VALIDATE와 거의 비슷하다.
EXAMPLE
아래와 같은 command들을 수행하여 backup하고자 하는 database file과 archived redo
log들이 실제로 backup될 수 있는지를 검증할 수 있다.
RUN {
ALLOCATE CHANNEL ch1 TYPE 'sbt_tape';
BACKUP VALIDATE
DATABASE
ARCHIVELOG ALL;
Note: MAXCORRUPT or PROXY parameter는 VALIDATE option과 함께 사용할 수 없다.
REFERENCE DOCUMENTS
NOTE:121109.1

Clint,
I ran the command lines you wrote me after i placed the database in Startup MOUNT state, RMAN gave error messages that the database needs to be open:
RMAN> SQL 'ALTER TABLESPACE USERTB2 OFFLINE IMMEDIATE';
sql statement: ALTER TABLESPACE USERTB2 OFFLINE IMMEDIATE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 11/04/2005 15:31:33
RMAN-11003: failure during parse/execution of SQL statement: ALTER TABLESPACE US
ERTB2 OFFLINE IMMEDIATE
ORA-01109: database not open
Then I ran the same command lines after I opened the database, RMAN gave error messages that "offline immediate disallowed unless media recovery enabled":
RMAN> SQL 'ALTER TABLESPACE USERTBS2 OFFLINE IMMEDIATE';
sql statement: ALTER TABLESPACE USERTBS2 OFFLINE IMMEDIATE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 11/04/2005 15:48:17
RMAN-11003: failure during parse/execution of SQL statement: ALTER TABLESPACE US
ERTBS2 OFFLINE IMMEDIATE
ORA-01145: offline immediate disallowed unless media recovery enabled
I am stuck again and need your help!
Thank you,
Mitra

How are Windows Server Backup and Command Line Tools used in vCSHB installation?

How are Windows Server Backup and Command Line Tools used during the installation of vCSHB? Is it required in all types of deployments (PtoV, VtoV, PtoP)? Is it used to create the files that are put in the file share for the second node to use during vCSHB installation or is it only used during a vCSHB clone operation of a Physical to Physical deployment? Are these tools not used in some deployments?

You need Windows Server Backup installed on source and destination, and during the installation of vCSHB the installer will invoke the wbadmin (Windows Server Backup Utility) and will backup configuration and application data (application data is optimal but can decrease the sync time after installation of secondary node). On the secondary node you will need only run the vCSHB installer and everything will be restored.
Check this blog entry for some more info about some problems in P2P deployment: http://www.vcoportal.de/2013/12/vmware-vcenter-server-heartbeat-restore-on-a-second-node-a-journey/

RMAN Parallel Backup Validate

Hi,
OS= Solaris 10
Database = 10gR2
I am using following script to validate the physical and logical corruption in the database through RMAN:
rman target /
RMAN> RUN {
CONFIGURE DEVICE TYPE DISK PARALLELISM 8;
ALLOCATE CHANNEL d1 DEVICE TYPE DISK;
ALLOCATE CHANNEL d2 DEVICE TYPE DISK;
ALLOCATE CHANNEL d3 DEVICE TYPE DISK;
ALLOCATE CHANNEL d4 DEVICE TYPE DISK;
BACKUP VALIDATE DATABASE;
RELEASE CHANNEL;
My machine has 4 CPUs.
I just want to verify that will the above RMAN script open up 4 channels in parallel and validate the database?
regards

Hi Fahd,
Can you please study the below link also from the forum.
Backup Time
Best regards,
Rafi.
http://rafioracledba.blogspot.com/

We wanted to perform backup from command prompt but we want

OS: :Linux
DB version: 10.2
I am doing weekly hot backup.
I used rman for my backup.
No issue on backup.
I just ran the backup succesufully (on 070307).
But Enterprise Manager is not updated.
Its still showing last backup performed on 07 Nov 2006.
But from command prompt by using rman its showing current backup (on 070307).
I think EM shown backup status only
if user used EM to perform backup.
Is it correct?
If yes how to fix this issue, we wanted to perform backup from command prompt but we want backup status should be updated in the EM simultaneously.
D

Hi,
Within EM it is assumed that a control file backup will take place unless you specifically ask it to perform through a recovery catalog. I can't remember at the moment how to do this as I am at home but when you go into the admin/maintenance side of EM there will be an option to chose recvoery catalog. However saying that, EM should still report back even if a control file backup has been carried out.
also i think if you are using a comand prompt then EM will not know about it. You will have to define the job from EM for it to register.
rgds
alan

RMAN Backup Validate

Hi,
We are having prod rman backup but not sure if it is valid one or not.
Can any one suggest me how to valdate if those backup pieces can be used to restore the db for cloning of dev instance.
Regards,
siva

Mohamed ELAzab wrote:
Hello,
You can use cross check backup.
Please view this Link:
http://ss64.com/ora/rman_crosscheck.html
Two wrong things,
1) Crosscheck is not the command to validate the restore but to check the physical existence of the backup pieces in comparison to the control file's repository. The op said,"We are having prod rman backup but not sure if it is valid one or not." So the restore validate is the command that's needed here based on what OP has said.
2) Please use official oracle documentation for the reference as the error correction is guaranteed over there compared to the external sites like the one you have linked which almost never update/correct their content.
Aman....

What actually RMAN "backup validate database" does?

OS: AIX 5.3L; DB: Oracle 10g R2
According to the RMAN doc, the validate actually run an integrity check on all datafiles and the archive logs if includes the "archivelog all" without creating any backupset. But I want to know what exact process Oracle engine is doing behind ? Because when I used it the first time, it took VARY long time to finish the validate process, the whole backup ( I followed the backup report as it was going). Then when I repeated it in my second backup process, the total backup time is back to normal as without it. Example: with my 31G DB, 6 and 1/2 hours first time, then 23 minutes for repeat.

I read that doc too. I think maybe I did not ask question more clearly. But I want to understand what Oracle really does when this process checks all the blocks of the datafiles physically? Did it log its process, so the next run will know what it did before for the same block. Remember I observed that my repeat of the validate run vary fast comparing to that of the first time. I also checked with the paging activity and the iostat of the AIX, I did not see too much changes. Since I am going to apply this backup scheme to my prod box (same AIX 5.3 platform), I need to locate a suitable time period to run the first level 0 backup.

Backup validate command

Similar Messages

Maybe you are looking for