Use transportable tablespaces to perform tablespace point-in-time recovery (TSPITR) - Oracle Tablespaces

Q.  You can use transportable tablespaces to perform tablespace point-in-time recovery (TSPITR).
- Published on 29 Jul 15

a. True
b. False

ANSWER: True
 

    Discussion

  • Nirja Shah   -Posted on 31 Aug 15
    - You can use the transportable tablespace feature to perform tablespace point-in-time recovery.

    - This method is similar to the O/S TSPITR, except you use the transportable tablespace feature to move recovered tablespaces from the clone database to the primary database.

    - The major difference between O/S TSPITR and TSPITR through transportable tablespaces is that for the former you must follow the special procedures for creating clone initialization parameter files, mounting the clone database, etc.

    - Performing TSPITR through transportable tablespaces relaxes this requirement.

    - If you restore backups to a different computer separate from the primary database, you can start the clone database as if it were the primary database, using the normal database MOUNT statement instead of the clone database MOUNT statement.

    - TSPITR through transportable tablespaces provides basically the same functionality as O/S TSPITR, but is more flexible since:
    1. You can recover dropped tablespaces, which you cannot do using O/S TSPITR.
    2. You can transport the recovered tablespaces from the clone database to a different database to test the procedure before making permanent changes to the primary database.

Post your comment / Share knowledge


Enter the code shown above:
 
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)