Even with the same DB_NAME, as long as the DB_UNIQUE_NAME parameter is
different, there will not be any conflicts. RMAN uses the DB_UNIQUE_NAME to distinguish
backups between databases that use the same flash recovery area.
Chapter 12: Using Recovery Manager (RMAN) 453
Validating Backups
Having multiple image backups or enough archived redo log files to support a recovery window
is of less value if there are problems with the live database files or control files. The RMAN
command backup validate database will simulate a backup, checking for the existence of the
specified files, ensuring that they are not corrupted. No backup files are created. This command
would be useful in a scenario where you can check for problems with the database or archived
redo logs proactively, giving you an opportunity to fix problems before the actual backup operation
or for scheduling additional time overnight to repair problems found during the day.
In the following example, we will validate the entire database along with the archived redo
logs after one of the redo log files is accidentally lost:
ASMCMD> cd 2007_08_27
ASMCMD> ls
thread_1_seq_91.280.631681211
thread_1_seq_92.281.631708219
thread_1_seq_93.282.631730443
thread_1_seq_94.283.631749691
thread_1_seq_95.284.631750213
ASMCMD> rm *95.*
You may delete multiple files and/or directories.
Are you sure? (y/n) y
ASMCMD>
. . .
RMAN> backup validate database archivelog all;
Starting backup at 04-SEP-07
using channel ORA_DISK_1
archived log +RECOV/dw/archivelog/2007_08_27/
thread_1_seq_95.
Pages:
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697