| Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02 |
|
|
View PDF |
| Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02 |
|
|
View PDF |
It is not always necessary to duplicate all tablespaces of a database. For example, you may plan to generate reports at the duplicate that require only a subset of tablespaces from your target database. RMAN DUPLICATE DATABASE can skip read-only tablespaces or tablespaces that are currently OFFLINE NORMAL. This section describes how to skip such tablespaces during DUPLICATE. It contains the following topics:
When you specify SKIP READONLY, RMAN does not duplicate the datafiles of read-only tablespaces. After duplication is complete, you can query the views in the duplicate database described in Table 13-2 and Table 13-3 to determine which datafiles were skipped. The STATUS and ENABLED columns describe the current status of the duplicate datafile.
When tablespaces are taken offline with the OFFLINE NORMAL option before a DUPLICATE operation, RMAN does not duplicate the datafiles of these tablespaces. After duplication, you can manually add or drop these tablespaces. Query the views in the duplicate database described in Table 13-4 and Table 13-5 to determine which datafiles are offline, based on the STATUS and ENABLED columns.
Table 13-4 Offline Tablespaces in V$ Views on Duplicate Database
| In the column ... | The value is ... |
|---|---|
|
|
|
|
|
|
|
|
|
Table 13-5 Offline Tablespaces in Data Dictionary Views on Duplicate Database
| View | In the column ... | The value is ... |
|---|---|---|
|
|
|
|
|
|
|
|
Note:
RMAN duplicates tablespaces that are taken offline with the
IMMEDIATE option, because such a tablespace requires recovery. As with online tablespaces, RMAN requires a valid backup for duplication.