問題描述

我們最近開始使用 AWS DMS 從 RDS 上的 Oracle 數(shù)據(jù)庫到 S3 的持續(xù)遷移(初始加載 + CDC)過程.數(shù)據(jù)庫正在使用 LogMiner.

We recently started the process of continuous migration (initial load + CDC) from an Oracle database on RDS to S3 using AWS DMS. The DB is using LogMiner.

我們檢測到的問題是 Update 類型的 CDC 記錄只包含被更新的數(shù)據(jù)，其余字段為空，因此簡單地將具有最大時間戳值的記錄視為有效的可能性丟失了.

the problem that we have detected is that the CDC records of type Update only contain the data that was updated, leaving the rest of the fields empty, so the possibility of simply taking as valid the record with the maximum timestamp value is lost.

有誰知道這是否可以更改或在 DMS 或 RDS 配置的哪個部分進(jìn)行觸摸，以便更新包含記錄的所有字段的信息?

Does anyone know if this can be changed or in what part of the DMS or RDS configuration to touch so that the update contains the information of all the fields of the record?

提前致謝.

推薦答案

表級別的補(bǔ)充日志記錄可能會增加記錄的內(nèi)容，但這也會增加為給定工作負(fù)載寫入的日志數(shù)據(jù)總量.

Supplemental Logging at table level may increase what is logged, but that will also increase total volume of log data written for a given workload.

來自不同供應(yīng)商的許多基于日志的數(shù)據(jù)復(fù)制產(chǎn)品需要在表級別進(jìn)行額外的補(bǔ)充日志記錄，以確保將更改前后數(shù)據(jù)更新的完整行數(shù)據(jù)寫入數(shù)據(jù)庫日志.

Many Log Based Data Replication products from various vendors require additional supplemental logging at the table level to ensure the full row data for updates with before and after change data is written to the database logs.

re:https://docs.oracle.com/database/121/SUTIL/GUID-D857AF96-AC24-4CA1-B620-8EA3DF30D72E.htm#SUTIL1582

通過 LogMiner 提取數(shù)據(jù)是可能的，但您需要評估它是否可以根據(jù)您需要的數(shù)據(jù)量進(jìn)行擴(kuò)展.

Pulling data through LogMiner may be possible, but you will need to evaluate if it will scale with the data volumes you need.

這篇關(guān)于帶有 CDC 的 AWS DMS.更新記錄只包括更新的字段.如何包括所有?的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網(wǎng)！