How the Amazon TimeHub team handled disruption in AWS DMS CDC task caused by Oracle RESETLOGS: Part 3
Database Blog
The article discusses how the Amazon TimeHub team handled disruption in AWS Database Migration Service (DMS) caused by Oracle RESETLOGS during database failover scenarios.
- Oracle RESETLOGS resets log sequence numbers, causing DMS tasks to fail
- The team evaluated three options for handling RESETLOGS disruption:
- Default AWS DMS RESETLOGS handling
- Restarting DMS task with specific timestamp/SCN
- Two-step task restart to mitigate potential data loss
- They developed a custom data validation framework using AWS Glue to:
- Detect RESETLOGS failures via CloudWatch alarms
- Validate data integrity after task restart
The solution helps avoid data discrepancies during unplanned database failovers and maintains data integrity between source and target systems.
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
Dec 13
2024
2024
How the Amazon TimeHub team designed a recovery and validation framework for their data replication framework: Part 4
Dec 13
2024
2024
How the Amazon TimeHub team designed resiliency and high availability for their data replication framework: Part 2
Mar 4
2024
2024
How the Amazon Timehub team built a data replication framework using AWS DMS: Part 1
Jul 9
2026
2026
Diagnose and resolve replica lag in Amazon RDS for Oracle replicas – 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.