Run Migration Job

After analyzing the CPAT report and fixing any issues, proceed with the migration.

The Zero Downtime Migration utility exports the objects from the source database and stores them in local storage. The utility pushes the export dump files to object storage using the OCI client utility. Finally, an OCI Object Storage import is executed to load the data into the destination Oracle Autonomous Database on Dedicated Exadata Infrastructure.

About Zero Downtime Migration Operational Phases

The Zero Downtime Migration service defines the migration process in units of operational phases. Zero Downtime Migration auto computes the migration workflow using defined operational phases based on configured input parameters, such as the target platform, backup medium, and so on. You can customize the workflow by inserting custom plug-ins on each of the operational phases. Zero Downtime Migration allows you to pause and resume the migration workflow at any chosen operational phase. Migration workflow-associated phases for a given operation can be listed. Phases that are performed on the source database server are listed with a _SRC suffix, and the phases associated with the target database server are listed with a _TGT suffix.

Run Migration Job

Submit a migration job as the zdmuser.

1. Run a migration job.
   The command resembles:

   [zdmuser@zdmhost ~]$ $ZDM_HOME/bin/zdmcli migrate database -rsp /home/zdmuser/template/zdm_logical_offline_pdb19c.rsp -sourcenode host_name.appsubnet.exadatainfrastr.oraclevcn.com -sourcesid PDB_name -srcauth zdmauth -srcarg1 user:opc -srcarg2 identity_file:/home/zdmuser/.ssh/id_rsa -srcarg3 sudo_location:/usr/bin/sudo 

   A job ID is returned to track the job status.
2. Monitor the migration job status using the job ID.
   The command resembles:

   [zdmuser@zdmhost ~]$ $ZDM_HOME/bin/zdmcli query job -jobid 3

3. Review the log files for additional details about each step.

After the migration job completes successfully, each step of the job is marked as COMPLETED.