We??™ll show how to record the existence of other backups made
outside of the database and perform some catalog maintenance. We??™ll also give a couple more
examples of the list and report commands.
Cataloging Other Backups
On occasion, we want the recovery catalog to include backups made outside of RMAN, such as
image copies made with operating system commands or with the asmcmd command, as in this
example:
ASMCMD> pwd
+DATA/dw/datafile
ASMCMD> ls
EXAMPLE.265.630244801
INET_INTL_STAR.269.632009933
INET_STAR.268.632004213
SYSAUX.257.630244581
SYSTEM.256.630244579
UNDOTBS1.258.630244583
USERS.259.632441707
USERS_CRYPT.267.630456963
ASMCMD> cp USERS.259.632441707 /u02/oradata/USERS.259.632441707
source +DATA/dw/datafile/USERS.259.632441707
target /u02/oradata/USERS.259.632441707
copying file(s)...
file, /u02/oradata/USERS.259.632441707, copy committed.
ASMCMD>
CAUTION
Image copies created with operating system commands must be
performed either while the database is shut down or by using the
alter tablespace . . . begin/end backup commands.
Chapter 12: Using Recovery Manager (RMAN) 471
Recording this image copy of the USERS tablespace is easy in RMAN using the catalog
command:
RMAN> catalog datafilecopy '/u02/oradata/USERS.259.632441707';
starting full resync of recovery catalog
full resync complete
cataloged datafile copy
datafile copy file name=/u02/oradata/
USERS.259.632441707 RECID=11 STAMP=632447886
RMAN>
Now that the image copy is recorded in the RMAN repository, it may be considered for use in
restore and recovery operations for the USERS tablespace.
Pages:
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715