Logging And Troubleshooting

Learn how to access logs and troubleshoot issues with Oracle Exadata Cloud Infrastructure Migration Utility.

Oracle Exadata Cloud Infrastructure Migration Utility Logs

The migration utility automatically creates logs for each job under /home/opc/exacloudmigration_data/logs when extracted to /home/opc. The main log records the steps performed for an operation, while the debug log contains detailed Java SDK call information for developer-level troubleshooting; filenames include the job ID, such as job_1_main.log and job_1_debug.log.

Read More: Oracle Exadata Cloud Infrastructure Migration Utility Logs

Review The Logs

For migration issues, first check the job status with exacloudmigration get_job_status -i <job number>, then review the corresponding job_<jobid>_main.log file. Check the known issues documentation, locate the Work Request ID in the main log, and review the request in One View. For Data Guard failures involving operations such as dgassociation, switchover, or failover, collect DBaaS diagnostic logs covering one hour before and after the incident, using a comma-separated database list when necessary.

Read More: Review The Logs

Upload The Logs To Service Request

If troubleshooting does not resolve the problem, create a Service Request under the Oracle Database service, selecting the migration utility category and the subcategory matching the affected migration type. Use exacloudmigration diag_collect to gather a default diagnostic bundle or specify a filename with -f; for Data Guard failures, also collect target-cluster DBaaS diagnostics for one hour before and after the issue, including multiple database names as a comma-separated list when required.

Read More: Upload The Logs To Service Request

Troubleshooting And Diagnostics

Additional troubleshooting guidance is available in the Oracle diagnostics-collection and system-troubleshooting documentation for both ExaDB-D and ExaDB-C@C. These resources explain how to collect diagnostic information and investigate issues affecting Exadata Cloud Infrastructure systems and Oracle Exadata Database Service on Cloud@Customer systems.
Read More: Troubleshooting And Diagnostics