Soru

Zorluk: ZorDatabase Migration and Schema Conversion using DMS and SCT

An enterprise is planning to migrate an on-premises Oracle 19c database containing several tables with large binary objects (LOBs) and complex PL/SQL packages to Amazon Aurora PostgreSQL-Compatible Edition. The migration must minimize downtime and maintain transactional consistency. Which actions should the Solutions Architect recommend to achieve this? (Select two.)

  1. Use the AWS Schema Conversion Tool (AWS SCT) to convert the Oracle database schemas and PL/SQL code to PostgreSQL-compatible formats, and install the AWS SCT extension pack on the target Aurora PostgreSQL DB cluster to emulate unsupported functions.Cevap
  2. Enable database-level and table-level supplemental logging on the source Oracle database, and run an AWS DMS replication task using Limited LOB mode with an optimized max LOB size to replicate the data and capture changes.Cevap
  3. C
    Deploy AWS Application Migration Service (MGN) to perform a block-level replication of the source Oracle server directly to the Aurora PostgreSQL DB cluster to automate the migration and bypass schema conversion.
  4. D
    Configure the AWS DMS replication task to target the reader endpoint of the Aurora PostgreSQL DB cluster to offload write operations during the migration and prevent performance degradation of the primary writer instance.
  5. E
    Configure the AWS DMS replication task to use Full LOB mode to replicate all binary data without truncation, and configure the replication task to automatically capture changes without modifying source logging settings.

Cevap

Use the AWS Schema Conversion Tool (AWS SCT) to convert the Oracle database schemas and PL/SQL code to PostgreSQL-compatible formats, and install the AWS SCT extension pack on the target Aurora PostgreSQL DB cluster to emulate unsupported functions. Additionally, enable database-level and table-level supplemental logging on the source Oracle database, and run an AWS DMS replication task using Limited LOB mode with an optimized max LOB size to replicate the data and capture changes.
The correct options are to use the AWS Schema Conversion Tool (AWS SCT) with its extension pack to convert and emulate the schema, and to enable supplemental logging on the source Oracle database while utilizing Limited LOB mode in the AWS DMS task. AWS SCT converts the schema to PostgreSQL format, and the extension pack provides emulation of features not native to PostgreSQL. Enabling supplemental logging is mandatory for AWS DMS to parse redo logs during Change Data Capture (CDC). Limited LOB mode optimizes replication performance by pre-allocating memory buffers for LOB columns.

Adım Adım Çözüm

1
Assess the source database schemas and convert them to the target engine format.
The Oracle schemas, including PL/SQL packages, are converted using the AWS Schema Conversion Tool (AWS SCT). An extension pack is applied to the target Aurora PostgreSQL DB cluster to emulate features like Oracle-specific functions.
Heterogeneous migrations require schema conversion before data migration. SCT handles the translation and provides an extension pack for compatibility.
2
Prepare the source Oracle database for Change Data Capture (CDC).
Database-level and table-level supplemental logging are enabled on the source Oracle database.
AWS DMS CDC requires supplemental logging on Oracle to identify which columns changed and to reconstruct the transaction logs.
3
Configure and run the AWS DMS task.
An AWS DMS task is created with Limited LOB mode configured to capture changes and perform the initial full load efficiently.
Limited LOB mode is optimal for migration performance, and setting a max LOB size prevents task performance degradation while ensuring LOB columns are migrated within defined limits.

Anahtar Kavram

Heterogeneous database migration using AWS Schema Conversion Tool (SCT) for schema conversion and AWS Database Migration Service (DMS) with Change Data Capture (CDC) and LOB configuration.
Bu soruyu puanla