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.

Parent topic: Logging and Troubleshooting

Create a Service Request

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

Table 4-1 Service Request details

Field	Value
Service Group	Oracle Database
Service	Oracle Cloud Infrastructure – Exadata Cloud Service
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.

Parent topic: Upload the logs to Service Request

Upload Logs to a Service Request

If a job fails during the migration process, collect and upload the following information to your Service Request (SR) to assist with troubleshooting.

Check the Utility version.
Run the following command to determine the version of Oracle Exadata Cloud Infrastructure Migration Utility:
```
/home/opc>./exacloudmigration -V
```
Retrieve failed job details.
Use the following command to view the details and status of the failed job:
```
/home/opc>./exacloudmigration get_job_status -i <jobid>
```
For example, failed job ID is 1:
```
/home/opc>./exacloudmigration get_job_status -i 1
```
Identify the Template Files used for the job.
Template files used during job execution are located under:
```
/home/opc> ./inputs/infra_<source_infra_name>/
```
The template file names are typically:
- infrastructure_inputs
- cloudvmcluster_inputs
- database_inputs
You can also identify the specific template file name from the get_job_status command output. Look for the line containing the text Command Executed.

For example:
```
2025-03-12T10:37:09.893Z [main] INFO - Fetching the status of the JobCommand Executed : /home/opc>./exacloudmigration delete_standby -i inputs/infra_infrax9m/vmcluster_ecmvm1/database_inputs -l testdb
Utility version
```
Collect Job log files
Compress the contents of the following log directory:
```
/home/opc>./exacloudmigration_data/logs/
```
Upload the zipped log folder to your Service Request.
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
```

Parent topic: Upload the logs to Service Request