Performing Oracle Cross-Platform Migration Using a Workflow

You can migrate Oracle databases that run on an AIX or a Solaris operating system to a Linux operating system using the Unix to Linux Oracle Migration Workflow.

Before You Begin

Verify that your environment meets the following requirements:

  • The source and destination hosts must meet the following requirements:
    • Are registered with the CommServe server.
    • Have the same directory structure.
    • Have the same version of Oracle.
    • The databases are in the OPEN mode.
  • The source host must have the following software installed:
    • MediaAgent
    • Oracle agent
    • File System agent
  • The destination server must have at least as much space as the source database, in order to stage the files before importing them to the destination database.
  • The staging path must meet the following requirements:
    • Has read/write permissions for the Oracle user on both the source and the destination.
    • Has enough space to store all the data files in the user-defined tablespaces.
  • If you want the workflow to import the database, the database name and path must be the same on both the source and destination hosts.
  • User-defined schemas on the destination database that have the same name as on the source database must be dropped on the destination database before the workflow runs.
  • Create a storage policy with a spool copy. For more information, see Enabling Spool Copy.
  • Download and deploy the Unix to Linux Oracle Migration Workflow workflow from Commvault Store. For instructions, see Download Workflows from Commvault Store.


  1. Log in to the Web Console.
  2. Click Forms.

    The Forms page appears.

  3. Click Unix to Linux Oracle Migration Workflow.

    The Unix to Linux Oracle Migration dialog box appears.

  4. Click OK.

    The source client selection dialog box appears.

  5. From the source client selection box, select the source client, and then click Next.

    The source database server options dialog box appears.

  6. Enter the following information about the backup operation.
    • Source instance: Select the Oracle SID on the source host.
    • Directory path to hold the image copy: Enter a location for the image copy dump.
    • Storage policy: Select the spool-enabled storage policy that you configured for the migration.
    • Number of RMAN channels for backup: Enter the number of streams that you want to use for the IntelliSnap backup operation.
    • To receive a notification when the database gets locked for the most recent backup, select the Notify me when locking the DB for last backup check box.
    • To allow converting the data to the new format and to import the database, select the Run the script to convert and import the DB check box.

      Note: Select this check box only when the source and the destination directory structure is the same and you want to redirect the datafiles to the same location. To redirect the datafiles to a different location, see Running the Script to Convert Datafiles for Oracle Cross-Platform Restore Operations.

  7. Click Continue.

    A message states that the IntelliSnap backup started.

  8. Click OK.

    When the workflow is ready to run the final backup, a message prompts you to confirm that you want to lock the database for the final backup.

  9. Click Confirm.

    After the final backup completes, a message prompts you to run an auxiliary copy operation in order to take additional copies of the backup image before proceeding with the migration.

    Run an auxiliary copy operation. For more information, see Performing an Auxiliary Copy.

  10. To resume the workflow, on the confirmation message, click Complete.
  11. To back up the image copy files, enter the following information:
    • Destination client name: Select the destination Linux client that you want to migrate the source database to.
    • Staging directory: Enter the location where you want to stage the image copy files from the source host.
    • User name: Enter the Oracle user who has the permissions to run the RMAN conversion and database import.
    • Password: Enter the password for the Oracle user.
  12. Click Next.


The workflow creates an Oracle subclient and runs an image copy IntelliSnap backup of the source Oracle database. After the first IntelliSnap backup, the workflow runs incremental backups of the database. During these backups, the database remains in the READ WRITE mode. During the final IntelliSnap backup, the workflow locks the database, backs up the image copy files, and then restores the files to the staging location on the destination host. After the restore, if you selected the Run the script to convert and import the DB check box, the workflow converts the data files and tablespaces to the new platform format using RMAN CONVERT and imports the database to the destination server.

Last modified: 9/22/2020 1:18:18 PM