Databases Reference
In-Depth Information
9.
Finally, the temporary instance is dropped:
Removing automatic instance
shutting down automatic instance
Oracle instance shut down
Automatic instance removed
auxiliary instance file +DG1/cdb1/datafile/sysaux.259.790448475 deleted
auxiliary instance file +DG1/cdb1/datafile/undotbs2.257.790448475 deleted
... and so on ...
If you encounter an error at any of the steps, it will be clearly visible in the above steps. The most common issues
that may come up during this activity are:
•
Backup does not have the tablespace that contains the table to be recovered
•
The table was not present at the SCN or timestamp given in the recover command
•
Not enough storage to restore the auxiliary database
•
Not enough memory to create the auxiliary instance
Here are the restrictions on the recover table process:
•
SYS owned tables can't be recovered.
recover table
works by performing a point in time recovery of the tablespace, which
is not allowed for SYSTEM and SYSAUX. Therefore, tables in these two tablespaces can't be
recovered with this command.
•
The
•
Tables can't be recovered on a physical standby database.
Recovering a Partition
Problem
You want to recover a single partition named P1 from a table named ACCOUNTS from the backup.
Solution
Follow the prerequisites explained in Recipe 13-22—e.g., there should be enough space in the auxiliary destination
to hold the tablespaces SYSTEM, SYSAUX, and the tablespace where the partition exists. Sufficient memory to run
another instance and the backup that contains the partition. After ensuring all those prerequisites are satisfied,
follow these steps in RMAN:
1.
Connect to RMAN target database:
RMAN> connect target "/ as sysdba"
2.
Recover the table's partition with this command:
RMAN> recover table scott.accounts:P1
2> until scn 1799975
3> auxiliary destination '+DG1';
This creates a table called ACCOUNTS_P1, which is a replica of the partition P1 of the table
ACCOUNTS.
