Which solution will meet these requirements?
Create primary key indexes, secondary indexes, and referential integrity constraints in the target database before starting the migration process.
Use AWS DMS to run the conversion report for Oracle to Aurora MySQL. Remediate any issues. Then use AWS DMS to migrate the data.
Use the M5 or C5 DMS replication instance type for ongoing replication.
Turn off automatic backups and logging of the target database until the migration and cutover processes are complete.
Explanations:
While creating indexes and constraints is important for performance and data integrity, doing this before the migration does not address the requirement for minimal downtime during the ongoing requests and migration process. These tasks can lead to additional overhead during migration.
This option correctly describes using AWS DMS to generate a conversion report, allowing for remediation of any issues before data migration. It also aligns with the goal of ensuring minimal downtime, as it allows for the source database to continue serving requests while the migration is planned and executed.
While using M5 or C5 DMS replication instances can be beneficial for replication tasks, the instance type alone does not ensure the effectiveness of the ongoing replication process or address potential downtime during migration. Other considerations, such as schema conversion and data consistency, are critical.
Turning off automatic backups and logging could lead to data loss or inconsistencies during the migration process. It is essential to maintain backups and logging to ensure data integrity and to facilitate recovery in case of any issues during migration. This option does not meet best practices for database management.
I suspect that the answer is:
Use AWS DMS to run the conversion report for Oracle to Aurora MySQL. Remediate any issues. Then use AWS DMS to migrate the data.