From an RMAN session, we will back up the tablespace along with the control file. In this
case, it??™s critical that we back up the control file because it contains the definition for the new
tablespace.
RMAN> report schema;
starting full resync of recovery catalog
full resync complete
Report of database schema for database with db_unique_name DW
FIGURE 12-6 Display backupset information with OEM
Chapter 12: Using Recovery Manager (RMAN) 441
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1 750 SYSTEM YES
+DATA/dw/datafile/system.256.630244579
2 803 SYSAUX NO
+DATA/dw/datafile/sysaux.257.630244581
3 60 UNDOTBS1 YES
+DATA/dw/datafile/undotbs1.258.630244583
4 5 USERS NO
+DATA/dw/datafile/users.259.630244583
5 100 EXAMPLE NO
+DATA/dw/datafile/example.265.630244801
6 500 USERS_CRYPT NO
+DATA/dw/datafile/users_crypt.267.630456963
7 100 INET_STAR NO
+DATA/dw/datafile/inet_star.268.632004213
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- -------------------- ----------- --------------------
1 60 TEMP 32767
+DATA/dw/tempfile/temp.264.630244787
RMAN> backup as backupset tablespace inet_star;
Starting backup at 30-AUG-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=152 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00007
name=+DATA/dw/datafile/inet_star.
Pages:
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683