Article Number: 000198348
PowerProtect: PPDM Backup: How to continue protecting an Oracle database that is migrated from non-CDB to CDB
Summary: This article explains the procedure to follow with PowerProtect Data Manager when a database is migrated from a non-multitenant container database (non-CDB) to a container database (CDB). ...
Article Content
Instructions
1- Make sure that the PowerProtect Data Manager version is 19.10 or later. If this is not the case, update the PowerProtect Data Manager to at least version 19.10.
2- Make sure that the versions of the client agent (agentservice or agentsvc) and RMAN agent are 19.10 or later on the Oracle Server. If this is not the case, update the client agent and RMAN agent to at least version 19.10.
NOTE: Versions earlier than 19.10 might include side effects, such as failures during deletion from the Oracle catalog. All these failures have been corrected in version 19.10. Steps 1 and 2 are optional but strongly recommended.
3- Edit the protection policy, and remove the original non-CDB database.
4- Use Oracle procedures and documentation to migrate the database from a non-CDB to a CDB.
NOTE: After you migrate the database from a non-CDB to a CDB, the status of the original non-CDB database appears in PowerProtect Data Manager as Not Detected. The status of the new CDB database appears as Available.
5- Edit the protection policy, and add the new CDB database to the policy.
6- Save the protection policy.
7- Start a full backup or wait for the schedule to run a full backup.
Note:
- There are no dependencies between the original non-CDB and new CDB databases.
- A level 0 or full backup is required to start protecting the new CDB database.
- With a self-service protection policy, start the backup from the Oracle Server or from the PowerProtect UI.
2- Make sure that the versions of the client agent (agentservice or agentsvc) and RMAN agent are 19.10 or later on the Oracle Server. If this is not the case, update the client agent and RMAN agent to at least version 19.10.
NOTE: Versions earlier than 19.10 might include side effects, such as failures during deletion from the Oracle catalog. All these failures have been corrected in version 19.10. Steps 1 and 2 are optional but strongly recommended.
3- Edit the protection policy, and remove the original non-CDB database.
4- Use Oracle procedures and documentation to migrate the database from a non-CDB to a CDB.
NOTE: After you migrate the database from a non-CDB to a CDB, the status of the original non-CDB database appears in PowerProtect Data Manager as Not Detected. The status of the new CDB database appears as Available.
Example:
In this example, the original non-CDB database is named orcl and the resulting CDB database is cdb1. The following figure shows the database status in PowerProtect Data Manager after the migration is complete.
In this example, the original non-CDB database is named orcl and the resulting CDB database is cdb1. The following figure shows the database status in PowerProtect Data Manager after the migration is complete.
5- Edit the protection policy, and add the new CDB database to the policy.
6- Save the protection policy.
7- Start a full backup or wait for the schedule to run a full backup.
Note:
- There are no dependencies between the original non-CDB and new CDB databases.
- A level 0 or full backup is required to start protecting the new CDB database.
- With a self-service protection policy, start the backup from the Oracle Server or from the PowerProtect UI.
Article Properties
Last Published Date
06 Sept 2022
Version
4
Article Type
How To