Databases Reference
In-Depth Information
How It Works
This type of recovery is used sometimes if you need to restore and recover only part of your database. For example, if
some data is accidentally modified in your production database, you can use this recovery to do the following:
1.
Copy production RMAN backup files to a nonproduction database server
2.
On the non-production database server, restore and recover just the system, sysaux, undo,
and other data files that you're interested in to a point in time just before the data was
erroneously modified
3.
Export the data out of the database's tablespaces to a point in time
4.
Use the exported data to fix data in your production database
Consider using a tablespace point-in-time recovery to restore and recover specific tablespaces to a previous
point in time (see recipe 12-10 for details).
Note
Performing Incomplete Recovery on a Pluggable Database
Problem
You want to restore a pluggable database to a prior point in time.
Solution
You can restore a pluggable database to a prior SCN, log sequence number, restore point, or timestamp. To do this
you must be connected to the root container database with sysdba or sysbackup privileges. You cannot perform this
operation while connected as SYS to the pluggable database. The steps for an incomplete recovery of a PDB are as
follows:
1.
Close the PDB.
2.
Specify a point in time in the past using an SCN, log sequence number, restore point, or
timestamp.
Issue the RESTORE and RECOVER commands.
3.
Open the PDB with the OPEN RESETLOGS clause
4.
This example follows the prior steps and performs an incomplete recovery on a pluggable database by specifying
an SCN for a prior point in the past:
ALTER PLUGGABLE DATABASE salespdb CLOSE;
run {
set until scn 2044500;
restore pluggable database salespdb;
recover pluggable database salespdb;
}
 
 
Search WWH ::




Custom Search