Recreating an Unrecoverable Database Deployment From a Backup to Cloud Storage
For a database deployment on Oracle Database Classic Cloud Service that hosts a single-instance database or a Data Guard configuration of single-instance databases, you can use the mrec
media recovery utility to recreate the deployment if it cannot be restored and recovered using the orec
command. This situation could occur if you've deleted critical configuration files or data files (such as the database redo log files, for example), or if something else has happened that caused the deployment to be lost.
The mrec
utility restores the database deployment to the point of the last backup. This is equivalent to restoring the database and configuration from an external tape device. The mrec
utility should be considered a last resource and used only when a database deployment cannot be restored in any other way.
Before You Begin
To recreate a deployment using the mrec
utility, the following condition must be met:
-
A backup of the original deployment, including configuration files, must exist in cloud storage. The recreated deployment will be restored up to the latest backup available in cloud storage (data files and configuration files). If such a backup doesn’t exist, you can't use
mrec
to restore the deployment.
You must also know the following:
-
The settings used to create the original deployment.
-
The credentials and URL of the Oracle Storage Cloud Service instance to which the original deployment is backed up.
-
The database system identifier (SID) associated with the original deployment.
Procedure
mrec
. If you are recreating a deployment hosting a Data Guard configuration, perform steps on the compute node hosting the primary database unless you are directed otherwise.