Review the logs

If you encounter any issues during the migration process, review the logs in the following order:

1. Check the job status:

   Run the following command to view the current status and details of the job:

   /home/opc> exacloudmigration get_job_status -i <job number>

   For example:

   /home/opc> exacloudmigration get_job_status -i 1

2. Locate and review the main utility log file for the job:

   /home/opc> ./exacloudmigration_data/logs/job_<jobid>_main.log

   For example:

   /home/opc/exacloudmigration_data/logs/job_1_main.log

3. Refer to the Known Issues section.

   If the issue is not listed or remains unresolved, proceed to the next step.

4. From the utility log file (for example, /home/opc/exacloudmigration_data/logs/job_1_main.log), locate the Work Request ID entry.

   For example:

   Work request ID:
   ocid1.coreservicesworkrequest.region1.sea.abzwkljsbsmatss5hee5nftkft2ex4dalerypxsdquw6mvzs222clls44ozq

5. Review the Work Request in One View.
6. Review DBaaS logs (for Data Guard failures)

   If the failure occurred during Data Guard operations such as dgassociation, switchover, or failover, collect and review DBaaS diagnostic logs for one hour before and after the issue:

   dbaascli diag collect --startTime YYYY-MM-DDTHH24:MM:SS --endTime YYYY-MM-DDTHH24:MM:SS --dbNames <value> --waitForCompletion false

   If you need to collect logs for multiple databases, specify a comma-separated list for the --dbNames parameter.

   For example:

   --dbNames db1,db2,db3