Performing Database Application Migration to Oracle Database as a Service

You can use the Commvault database application migration feature to move your database to the Oracle Database as a Service (DBaaS) cloud.

The Commvault software automates the following processes:

  • Capturing the application server physical configuration.

  • Protecting the application data

  • Creating the Oracle service and the database

  • Provisioning the storage

  • Installing the Commvault Oracle Agent software on the Oracle DBaaS so that you can run backups on the migrated database

  • Restoring the data

  • Validating the restore

About This Task

The following configurations are supported:

  • Oracle 11gR2, Oracle 12CR1, Oracle 12CR2

  • Oracle Standard or Enterprise Editions

  • Single instances

Before You Begin

  1. Have the backup administrator configure the firewall for application migration.

  2. Have the backup administrator configure the Oracle DBaaS VM lifecycle policy.

    Note: Make sure that the backup administrator has the Oracld DBaaS SSH keys.

  3. Make sure that you have the following information:

    • The Oracle Service name

    • The URL to the Oracle cloud storage

      This is where Oracle stores the database datafiles

    • The Oracle VM lifecycle policy


  1. From the navigation pane, go to Solutions > Databases > DB Instances.

    The Instances page appears.

  2. On the Instances tab, from the View list next to Instances, select Oracle.

    The Instances page for Oracle appears.

  3. Click the instance.

    The instance page appears.

  4. On the upper-right corner of the page, click the menu icon Admin Console menu icon (3 vertical dots), and then click Migrate to cloud.

    The Migrate to cloud page appears.

  5. Specify the cloud destination information.

    1. From the Cloud vendor list, select Oracle DBaaS.

    2. From the Provisioning Policy list, select the lifecycle policy.

    3. In the Service name box, type the Oracle DBaaS name.

      The Commvault software creates a new service in the cloud.

  6. Expand the Service configuration node, and then specify the service configuration.

    1. From the Metering frequency list, select when the payment option, for example monthly.

    2. From the Software release list, select the Oracle version.

    3. From the Software edition list, select the Oracle edition.

    4. From the Database type list, select Single instance.

    The software creates the Oracle instance with the selected options.

  7. Expand the Node configuration node, and then specify the database configuration.

    1. In the Database name box, type the database name.

      The database name can be the same as or different from the source database name.

    2. In the SYS password box, type the password for the Oracle database.

    3. In the Usable database storage box, type amount of storage that the database uses. You can enter a value between 15GB and 2048GB.

    4. From the Compute shape list, select the database computing power.

    5. In the Listener port box, type listener port number.

    6. The Commvault software automatically configures a JSON rule that defines what hosts can access the database. To modify the rule,in the Access rule JSON box, type the new commands.

  8. Specify the backup options.

    1. From the Backup service list, select the backup service.

    2. If you select Cloud storage only, then in the Cloud storage container box, type the URL to the Oracle cloud storage.

  9. Expand the Firewall configuration node, and then specify the firewall options.

    • If the Oracle server cannot communicate with Commvault, then make the following selections:

      • Select the There is a firewall between the client machine check box.

      • Select CommServe can open a connection towards client machines.

      • Best Practice: In the CommServe HTTP/HTTPS tunnel port box, type 443 because it is the HTTPS port.

    • If the Oracle DBaaS has a proxy server, then make the following selections:

      • Select the There is a firewall between the client machine check box.

      • Select CommServe is reachable only through a proxy.

      • From the Proxy client list, select the Oracle Proxy client

  10. Expand the Migration options node, and then specify the migration options.

    1. From the Migrate using list, select the vendor that performs the backup.

      Best Practice: Select Commvault so that you can take advantage of features such as data aging and scheduling.

      If you want to use the Oracle backup as a service option, then verify The Oracle requirements. For more information, see Oracle Database Backup.

    2. In the Migration area, select whether this operation is a one-time operation, or continuous.

      • To have this be a one-time operation, select One time.

      • To have this a continuous operation that uses the Live Sync feature, select Run a new full backup.

    3. In the Baseline area, select the backup to use for migration

      • To use the latest full backup, select Use most recent full backup.

      • To run a new backup for the Live Sync operation, select Run a new full backup.

    4. To have the destination database come up in standby mode, select the Restore Destination in Standby Mode check box.

    5. In the Number of Streams box, type the number of streams that the software will use for the replication operation.

    6. In the Post migration validation script box, type the full path and script name for the script that you use to validate the Oracle database.

  11. Click Submit.


The Commvault software creates the service and database, and then migrates the database and application.

There are 2 jobs for the migration, a VM provisioning job and a backup job.

What to Do Next

You can control or view the job. For more information, see Jobs.

Note: If the destination Oracle SID has a different value from the source Oracle SID (because you are performing a cross-instance migration), then perform the following steps when the job goes to a PENDING state.

  1. Log on to the DBaaS instance.

  2. Shut down the database, and then take a backup of the existing init file.

  3. Set the db_name parameter in the init file to the source instance name.

  4. Set the db_unique_name parameter in the init file to the new target database instance name.

  5. Continue the restore, and then open the database with the resetlogs option.

  6. Use the Oracle NID utility to rename the database.