Databases Reference
In-Depth Information
sysbackup
privileges and restore and recover all data files associated with the database. Since the data files associated
with the root system tablespace are being restored, the database must be started in mount mode (and not open):
$ rman target /
RMAN> startup mount;
RMAN> restore database;
RMAN> recover database;
RMAN> alter database open;
Keep in mind that when you open a container database, this does not by default open the associated pluggable
databases. You can do that from the root container as follows:
RMAN> alter pluggable database all open;
Restoring and Recovering Root Container Data Files
If just data files associated with the root container have been damaged, you can restore and recover at the root level.
In this example, the root container's system data file is being restored, so the database must not be open. The
following commands instruct RMAN to restore only the data files associated with the root container database via the
keyword
root
:
$ rman target /
RMAN> startup mount;
RMAN> restore database root;
RMAN> recover database root;
RMAN> alter database open;
In the prior code, the
restore database root
command instructs RMAN to restore only data files associated
with the root container database. After the container database is opened, you must open any associated pluggable
databases. You can do so from the root container as follows:
RMAN> alter pluggable database all open;
You can check on the status of your pluggable databases via this query:
SQL> select name, open_mode from v$pdbs;
Restoring and Recovering a Pluggable Database
You have two options for restoring and recovering a pluggable database:
•
Connect as the container root user and specify the pluggable database to be restored.
•
Connect directly to the pluggable database as a privileged pluggable level user and issue
restore and recover commands.
