A municipal permitting database on Oracle must move to Amazon Aurora PostgreSQL. Architects need schema conversion assessment plus ongoing data migration. Which combination should they select?
Select an answer to reveal the explanation.
Short Explanation
Changing Oracle dialects to Aurora PostgreSQL is a translation job plus a moving job. SCT tells you how painful the schema work is; DMS actually hauls the data—use both, not wishful restore magic.
Full Explanation
A municipal permitting database on Oracle moving to Amazon Aurora PostgreSQL needs both schema conversion assessment and ongoing data migration. Select AWS Schema Conversion Tool to assess conversion effort and AWS DMS to migrate the data—assessment plus replication is the standard pairing for heterogeneous database moves in civic permitting platforms. Amazon Macie alone to rewrite PL/SQL packages into PostgreSQL fails because Macie discovers sensitive data in object storage; it does not convert database schemas. AWS Backup restore of Oracle RMAN files directly onto Aurora PostgreSQL storage fails engine incompatibility—you cannot restore Oracle RMAN backups onto Aurora PostgreSQL storage as a conversion path. Amazon Athena CREATE TABLE AS to clone the live Oracle instance in place fails because Athena queries analytics data lakes; it is not an OLTP Oracle-to-Aurora migration engine. Exam caveat: SCT assesses heterogeneous conversion; DMS moves and syncs the data. Operational check: run SCT assessment reports for action items, remediate incompatible objects, set DMS source and target endpoints with CDC if downtime budgets require it, validate permitting row counts and critical queries on Aurora, then cut over under change control.