Known Issues

Learn about known issues and their workarounds for Oracle Exadata Cloud Infrastructure Migration Utility.

Creation Of Data Guard Association Fails

Data Guard association creation fails with DBAAS-70658 when the primary and standby clusters have inconsistent versions of the dbcs-agent RPM, and potentially dbaastools. Verify installed package versions on every node, then align them across both clusters by updating the agent, admin agent, and dbaastools packages using the appropriate dbaascli commands and packages obtained from Oracle Support or the cloud operations team.

Create Database From Backup Or Data Guard Association Fails

Creating a database from backup or establishing a Data Guard association can fail with DBT-09101 when mandatory target-environment prerequisites are unmet. Review the operation’s trace.log file to identify missing requirements, resolve them according to the installation guidance, and retry the operation.

When To Configure Manual Data Guard

Manual Data Guard configuration is required for migrations between ExaDB-D and ExaDB-C@C because the utility does not support enabling Data Guard, switchover, or failover across these different service types. Customers can duplicate the source database with dbaascli database duplicate and configure Data Guard Broker manually, or use Zero Downtime Migration to automate the process.

Does The Utility Support Cross-Tenancy Migration

The utility supports cross-tenancy migration of infrastructure, VM clusters, and database homes; however, Oracle Exadata Database Service currently does not support Data Guard associations between source and target databases during cross-tenancy migrations.

Cluster Verification Failures Due To Hostname Resolution Issues

Cluster verification can fail for ASM integrity, node connectivity, and hosts-file checks when dual IPv4 and IPv6 stacks cause hostnames to resolve inconsistently across nodes, producing PRVG-13632 errors. This known issue is fixed in the 19.26.0.0.250121 Oracle Clusterware Release Update for Grid Infrastructure and RDBMS homes; upgrade to database version 19.26 or later, or, as a less-preferred workaround, disable dual-stack networking on the compute nodes’ admin network before retrying.
Read More: Cluster Verification Failures Due To Hostname Resolution Issues