A company is planning to migrate an on-premises Oracle database to an Amazon Aurora PostgreSQL DB cluster. A solutions architect uses the AWS Schema Conversion Tool (SCT) to convert the database schema and configures an AWS Database Migration Service (DMS) replication task using the Full Load and ongoing replication (CDC) option. The Full Load phase completes successfully, but the DMS replication task transitions to a failed state shortly after the Change Data Capture (CDC) phase starts. Which of the following is the most likely cause of this failure?
- The source Oracle database was not configured with supplemental logging enabled, preventing AWS DMS from reading the change data from the redo logs.Cevap
- BThe target Amazon Aurora PostgreSQL DB cluster was not configured with binary logging (binlog) enabled, which is required for AWS DMS to write ongoing changes during the CDC phase.
- CThe migration path was incorrectly classified as replatforming instead of refactoring in the AWS Schema Conversion Tool (SCT), causing the DMS task to fail during schema constraint validation.
- DThe target Amazon Aurora PostgreSQL DB cluster's secondary reader instance was not configured with Multi-AZ replication enabled, causing the CDC phase to fail when trying to synchronize read traffic.
Cevap
The source Oracle database was not configured with supplemental logging enabled, preventing AWS DMS from reading the change data from the redo logs.
The correct answer is correct because AWS DMS CDC tasks require supplemental logging to be enabled on the source Oracle database. This allows DMS to capture the full row changes from the Oracle redo logs. If supplemental logging is not enabled, the DMS task will fail to replicate ongoing changes after the full load completes.
Adım Adım Çözüm
Anahtar Kavram
Enabling source database logging mechanisms (such as supplemental logging for Oracle or binary logging for MySQL) is a mandatory prerequisite for AWS DMS Change Data Capture (CDC) tasks.
Tahmini Süre:2m 0s