Home icon

Filter transactions from users with AWS DMS from an Oracle database

Database Blog



This article provides a solution to replicate ongoing changes from an Oracle Multitenant database to Amazon S3 using AWS DMS, while identifying transactions from specific users. The solution enables filtering or processing those transactions in downstream data pipelines.

Specifically, the article covers:

  • Solution overview and prerequisites
  • Creating a source endpoint for the Oracle Multitenant database and a target endpoint for Amazon S3
  • Configuring an AWS DMS replication task with transformation rules to add flags for identifying transactions from specific users
  • Validating the replicated data in Amazon S3
  • Cleaning up the resources


Go to article

The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.

Related articles

Feb 20
2024
Reference guide to analyze transactional data in near-real time on AWS
Feb 7
2024
Cost optimize database migrations with AWS DMS: Part 1
Jun 30
2026
Manage long-running transactions for AWS DMS performance
Feb 7
2024
Cost optimize database migrations with AWS DMS: Part 2

The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.