Performing Oracle Advanced Recovery - OCP: Oracle Database 12c Administrator Certified Professional - page 299

e xeRCiSe 7.1 (continued)
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics
and Real Application Testing options
SQL> select name, open_mode from v$database;
NAME OPEN_MODE
--------- ----------
NEWORCL READ WRITE
If you want to run this exercise again after the first successful run, you will need to per-
form these steps:
1. Shut down the auxiliary instance (now it's a new database!).
2. Remove the spfile assigned to the auxiliary instance.
3. Start up the auxiliary instance with STARTUP NOMOUNT .
4. Run this exercise again starting at step 11.
Performing an RMAN Tablespace
Point-in-Time Recovery
As you may recall, when you do a point-in-time recovery of an Oracle database, you have
to restore the entire database to the point in time selected. There are times when you may
want to restore a specific tablespace to a specific point in time. DBAs have been doing
this type of recovery manually for a long time. Simply, they restore a backup to another
database on the same or a different server to the point in time they want to restore the
tablespace to. They then export the objects they want to restore (or use transportable
tablespaces) to the original database.
Of course, this is a lot of manual work. RMAN automates tablespace point-in-time
recovery (TSPITR) for you, making recovery much easier to perform. In this section, we
will address TSPITR. We will first look at the TSPITR-related prerequisites and consider-
ations and then look at the aftereffects of a TSPITR. We will then look into setting up for
and executing a TSPITR.