Refreshing DB Systems Environment
You can refresh DB Systems environments managed by Cloud Manager from a backup in Object Store or from another DB system managed by Cloud Manager.
The RMAN database backup for an on premise environment lifted to Cloud Manager resides in the Object Store.
Backups for other DB Systems environments in Cloud Manager are stored in OCI block storage.
Refresh supports:
Refresh database only.
Refresh environment which includes database, PS App Home and PS Cust Home.
Important! The source and target database must be on the same version. Source environment backup must contain spfile.
To refresh an environment:
Perform a backup of the environment prior to the refresh. Before starting the Refresh, ensure that the backup has completed.
Navigate to the environment card on the Environments page.
Select Refresh from the actions for the DB Systems environment you want to refresh.
On the Refresh page, select the Source Type.
Enter the values for the backup.
Click Refresh.
Refreshing from Object Store
This example illustrates the fields and controls on the Add Refresh page where Source Type is Object Store. You can find definitions for the fields and controls later on this page.

Field or Control |
Description |
---|---|
Source Type |
Select the Object Store from the drop down list. |
Compartment Name |
Select the compartment used when the backup was taken using DBCLI (database command line interface) or Oracle Database Cloud Backup Module (ODCBM). |
Bucket Name |
Select the bucket name used when the backup was taken using DBCLI (database command line interface) or Oracle Database Cloud Backup Module (ODCBM). |
App Refresh |
Select the name of the application backup to refresh PS App Home and PS Cust home. Leave this field blank if you want to refresh the database only. |
Source TDE Key File Path |
If TDE is enabled on the source database enter the TDE key file path. |
Source TDE KeyStore (Wallet) Password |
If TDE is enabled on the source database enter the TDE KeyStore (Wallet) Password. |
OCI Auth Token |
Enter the OCI Auth Token for the source database. |
Source PDB Name |
Select the name used when the backup was taken using DBCLI (database command line interface) or Oracle Database Cloud Backup Module (ODCBM). |
Source DBID |
The source DBID is available during the RMAN backup stage, user must have the source DBID available. |
Source Tag Name |
The tag name that was specified during the RMAN backup. |
Source RMAN Backup Password |
Enter the RMAN backup password. This field only applies to non-TDE databases. |
Pre Refresh Custom script |
Select an uploaded script to run prior to refreshing the environment. This script is run from a middle tier belonging to the target environment. |
Post Refresh Custom script |
Select an uploaded script to run post refreshing the environment. This script is run from a middle tier belonging to the target environment. |
Target MT DMS Path |
Path to Data Mover scripts on the target middle tier node. |
Note: Application DPK contains the absolute path in Cloud Manager for PS_APP_HOME and PS_CUST_HOME. If application DPK only includes PS_APP_HOME, only PS_APP_HOME of target will be refreshed, otherwise both PS_APP_HOME and PS_CUST_HOME will be refreshed.
Refreshing from OCI Backup
This example illustrates the fields and controls on the Add Refresh page where Source Type is OCI Backup. You can find definitions for the fields and controls later on this page.

Field or Control |
Description |
---|---|
Source Type |
Select OCI Backup from the drop down list. |
Environment Name |
Select the environment to refresh from the drop down list. |
Backup ID |
Select the Backup ID from the drop down list. |
Use Latest Backup |
Select Yes to use the latest backup. |
App Refresh |
Select Yes to refresh PS App Home and PS Cust Home as well as the database. Select No for a database refresh only. |
Source TDE KeyStore (Wallet) Password |
The Source Wallet password is the same as the Database Administrator password. |
Pre Refresh Custom script |
Select an uploaded script to run prior to refreshing the environment. This script is run from a middle tier belonging to the target environment. |
Post Refresh Custom script |
Select an uploaded script to run post refreshing the environment. This script is run from a middle tier belonging to the target environment. |
Target MT DMS Path |
Path to Data Mover scripts on the target middle tier node. |
Retrieving Failed Refresh
Important! Before doing refresh make sure that an environment backup is done.
To retrieve failed refresh:
Select Details > Environment Details and click Refresh.
Environment may come to Running state.
If status updates to Not Started, check the following:
PDB, CDB name after refresh may differ from the actual. Correct the names.
DB Admin, access usernames and passwords may differ from actual. Correct DB credentials.
If status still results in failed status, check Details > Provision Task Status.
If failure is in INFRA task, retry from Provision Task Status page.
If that does not work, use the backup and restore feature to restore the environment.
Make sure spfile is present.