A company plans to transition their self-managed Oracle database to Amazon Aurora PostgreSQL-Compatible Edition. The database schemas have already been converted and applied to the target database. A Solutions Architect sets up an AWS Database Migration Service (AWS DMS) task configured for full load and ongoing replication (CDC). The full load phase completes successfully, but the task halts immediately when transitioning to the replication phase. Which two configuration steps must be performed on the source database to support ongoing replication? (Select two.)
- Ensure that the source database is configured to run in ARCHIVELOG mode.Answer
- Enable minimal supplemental logging and table-level supplemental logging on the source database.Answer
- CEnable supplemental logging on the target database tables.
- DConfigure the target database to write changes to local write-ahead logs (WAL) before applying them.
- EConfigure the AWS DMS source endpoint with extra connection attributes to disable the reading of online redo logs.
Answer
To support ongoing replication (CDC) from a source Oracle database, you must configure the source database to run in ARCHIVELOG mode and enable minimal supplemental logging and table-level supplemental logging on it.
To perform ongoing replication (CDC) from an Oracle source database, AWS DMS must read the transaction logs. This requires the source database to be in ARCHIVELOG mode so that transaction log files are archived and accessible. Additionally, supplemental logging must be enabled on the source database so that it writes sufficient column data to the redo logs for DMS to reconstruct the database changes.
Step-by-Step Solution
Key Concept
Configuring the source database transaction logs (ARCHIVELOG mode and supplemental logging) is mandatory for AWS DMS Change Data Capture (CDC) replication to succeed.