Upload the logs to Service Request

If the issue persists after reviewing the logs, create a Service Request (SR) and attach the required details and log files.

• Create a Service Request
  
• Upload Logs to a Service Request
  

Create a Service Request

When creating an SR for Oracle Exadata Cloud Infrastructure Migration Utility issues, use the following details for proper routing.

Table 5-1 Service Request details

Field	Value
Service Group	Oracle Database
Service	For ExaDB-D → Oracle Cloud Infrastructure – Exadata Cloud Service For ExaDB-C@C → Oracle Cloud Infrastructure – Exadata Cloud@Customer
Service Category	Oracle Exadata Cloud Infrastructure Migration Utility
Subcategory	Infrastructure Migration VM Cluster Migration Database Migration Other Migrations

Note:

Select the subcategory that best matches the type of migration operation where the issue occurred.

Upload Logs to a Service Request

If a job fails during the migration process, use the command below to collect diagnostic information and logs, then upload them to your Service Request (SR) to help with troubleshooting.

1. To collect diagnostic information and logs without specifying a file name (default: diagnostics-<ddmmyy-timestamp>.zip):

   exacloudmigration diag_collect

2. To collect diagnostic information and logs with a specified file name:

   exacloudmigration diag_collect -f diag_bundle.zip

3. Collect additional logs (if applicable).

   If the failure occurred during Data Guard operations such as dgassociation, switchover, or failover, collect additional diagnostic logs from the target cluster.

   Run the following command to collect 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 of database names for the --dbNames parameter.

   For example:

   --dbNames db1,db2,db3