AWS Security ChangesHomeSearch

AWS dms high security documentation change

Service: dms · 2026-03-19 · Security-related high

File: dms/latest/userguide/CHAP_Tasks.AssessmentReport.Oracle.md

Summary

Added four new premigration validation checks: 1) Target endpoint not a read replica, 2) Oracle target CONTEXT indexes check for direct path load, 3) Enabling FailTasksOnLobTruncation with limited LOB mode, 4) Enabling EnableHomogenousPartitionOps for partition DDL replication

Security assessment

The addition of 'Validate that FailTasksOnLobTruncation is enabled when using limited LOB mode' directly addresses data integrity by preventing silent LOB truncation. This change explicitly documents a security safeguard against data loss scenarios, which is a security-relevant data integrity concern. The other validations are operational checks without explicit security implications.

Diff

diff --git a/dms/latest/userguide/CHAP_Tasks.AssessmentReport.Oracle.md b/dms/latest/userguide/CHAP_Tasks.AssessmentReport.Oracle.md
index 7aa1b457f..79ee965cd 100644
--- a//dms/latest/userguide/CHAP_Tasks.AssessmentReport.Oracle.md
+++ b//dms/latest/userguide/CHAP_Tasks.AssessmentReport.Oracle.md
@@ -5 +5 @@
-Validate that limited LOB mode only is used when BatchApplyEnabled is enabledValidate if tables on the source has columns without scale specified for the Number data typeValidate triggers on the target databaseValidate if source has archivelog DEST_ID set to 0Validate if secondary indexes are enabled on the target database during full-loadValidate if tables used in the DMS task scope with BatchApplyEnabled have more than 999 columnsCheck supplemental logging on database levelValidate if required DB link is created for StandbyOracle validation for LOB datatype and if binary reader is configuredValidate if the database is CDBCheck the Oracle Database EditionValidate Oracle CDC method for DMSValidate Oracle RAC configuration for DMSValidate if DMS user has permissions on targetValidate if supplemental logging is required for all columnsValidate if supplemental logging is enabled on tables with Primary or Unique keysValidate if there are SecureFile LOBs and the task is configured for Full LOB modeValidate whether Function-Based Indexes are being used within the tables included in the task scope.Validate whether global temporary tables are being used on the tables included in the task scope.Validate whether index-organized tables with an overflow segment are being used on the tables included in the task scope.Validate if multilevel nesting tables are used on the tables included in the task scope.Validate if invisible columns are used on the tables included in the task scope.Validate if materialized views based on a ROWID column are used on the tables included in the task scope.Validate if Active Data Guard DML Redirect feature is used.Validate if Hybrid Partitioned Tables are used.Validate if schema-only Oracle accounts are usedValidate if Virtual Columns are usedValidate whether table names defined in the task scope contain apostrophes.Validate whether the columns defined in the task scope have XMLType, Long, or Long Raw datatypes and verify the LOB mode configuration in the task settings.Validate whether the source Oracle version is supported by AWS DMS.Validate whether the target Oracle version is supported by AWS DMS.Validate whether the DMS user has the required permissions to use data validation.Validate if the DMS user has permissions to use Binary Reader with Oracle ASMValidate if the DMS user has permissions to use Binary Reader with Oracle non-ASMValidate if the DMS user has permissions to use Binary Reader with CopyToTempFolder methodValidate if the DMS user has permissions to use Oracle Standby as a SourceValidate if the DMS source is connected to an application container PDBValidate if the table has XML datatypes included in the task scope.Validate whether archivelog mode is enabled on the source database.Validates the archivelog retention for RDS Oracle.Validate if the table has Extended datatypes included in the task scope.Validate the length of the object name included in the task scope.Validate if the DMS source is connected to an Oracle PDBValidate if the table has spatial columns included in the task scope.Validate if the DMS source is connected to an Oracle standby.Validate if the source database tablespace is encrypted using TDE.Validates if the source database uses Automatic Storage Management (ASM)Validate if batch apply is enabled and whether the table on the target Oracle database has parallelism enabled at the table or index levelRecommend “Bulk Array Size” parameter by validating the tables in the task scopeValidate if HandleCollationDiff task setting is ConfiguredValidate if table has primary key or unique index and its state is VALID when DMS validation is enabledValidate if Binary Reader is used for Oracle Standby as a sourceValidate if the AWS DMS user has the required directory permissions to replicate data from an Oracle RDS Standby database.Validate the type of Oracle Standby used for replicationValidate if required directories are created for RDS Oracle standbyValidate if Primary Key or Unique Index exists on target for Batch ApplyValidate if both Primary Key and Unique index exist on target for Batch ApplyValidate if unsupported HCC levels are used for Full LoadValidate if unsupported HCC levels are used for Full Load with CDCValidate if unsupported HCC compression used for CDCCDC Recommendation based on source compression methodCheck if batch apply is enabled and validate whether the table has more than 999 columnsCheck Transformation Rule for Digits RandomizeCheck Transformation Rule for Digits maskCheck Transformation Rule for Hashing maskVerify that Data Validation task settings and Data Masking Digit randomization are not enabled simultaneouslyVerify that Data Validation task settings and Data Masking Hashing mask are not enabled simultaneouslyVerify that Data Validation task settings and Data Masking Digit mask are not enabled simultaneouslyValidate that replication to a streaming target does not include LOBs or extended data type columnsValidate that CDC-only task is configured to use the OpenTransactionWindow endpoint settingValidate that at least one selected object exists in the source databaseValidate that target foreign key constraints are disabled for migrationValidate that the Oracle database and AWS DMS versions are compatibleValidate that secondary constraints and indexes (non-primary) are present in the source databaseValidate that session timeout settings (IDLE_TIME) are set to UNLIMITEDValidate that the AWS DMS user has all required permissions on the source databaseValidate that XMLTYPE or LOB columns exist when Oracle LogMiner is used
+Validate that limited LOB mode only is used when BatchApplyEnabled is enabledValidate if tables on the source has columns without scale specified for the Number data typeValidate triggers on the target databaseValidate if source has archivelog DEST_ID set to 0Validate if secondary indexes are enabled on the target database during full-loadValidate if tables used in the DMS task scope with BatchApplyEnabled have more than 999 columnsCheck supplemental logging on database levelValidate if required DB link is created for StandbyOracle validation for LOB datatype and if binary reader is configuredValidate if the database is CDBCheck the Oracle Database EditionValidate Oracle CDC method for DMSValidate Oracle RAC configuration for DMSValidate if DMS user has permissions on targetValidate if supplemental logging is required for all columnsValidate if supplemental logging is enabled on tables with Primary or Unique keysValidate if there are SecureFile LOBs and the task is configured for Full LOB modeValidate whether Function-Based Indexes are being used within the tables included in the task scope.Validate whether global temporary tables are being used on the tables included in the task scope.Validate whether index-organized tables with an overflow segment are being used on the tables included in the task scope.Validate if multilevel nesting tables are used on the tables included in the task scope.Validate if invisible columns are used on the tables included in the task scope.Validate if materialized views based on a ROWID column are used on the tables included in the task scope.Validate if Active Data Guard DML Redirect feature is used.Validate if Hybrid Partitioned Tables are used.Validate if schema-only Oracle accounts are usedValidate if Virtual Columns are usedValidate whether table names defined in the task scope contain apostrophes.Validate whether the columns defined in the task scope have XMLType, Long, or Long Raw datatypes and verify the LOB mode configuration in the task settings.Validate whether the source Oracle version is supported by AWS DMS.Validate whether the target Oracle version is supported by AWS DMS.Validate whether the DMS user has the required permissions to use data validation.Validate if the DMS user has permissions to use Binary Reader with Oracle ASMValidate if the DMS user has permissions to use Binary Reader with Oracle non-ASMValidate if the DMS user has permissions to use Binary Reader with CopyToTempFolder methodValidate if the DMS user has permissions to use Oracle Standby as a SourceValidate if the DMS source is connected to an application container PDBValidate if the table has XML datatypes included in the task scope.Validate whether archivelog mode is enabled on the source database.Validates the archivelog retention for RDS Oracle.Validate if the table has Extended datatypes included in the task scope.Validate the length of the object name included in the task scope.Validate if the DMS source is connected to an Oracle PDBValidate if the table has spatial columns included in the task scope.Validate if the DMS source is connected to an Oracle standby.Validate if the source database tablespace is encrypted using TDE.Validates if the source database uses Automatic Storage Management (ASM)Validate if batch apply is enabled and whether the table on the target Oracle database has parallelism enabled at the table or index levelRecommend “Bulk Array Size” parameter by validating the tables in the task scopeValidate if HandleCollationDiff task setting is ConfiguredValidate if table has primary key or unique index and its state is VALID when DMS validation is enabledValidate if Binary Reader is used for Oracle Standby as a sourceValidate if the AWS DMS user has the required directory permissions to replicate data from an Oracle RDS Standby database.Validate the type of Oracle Standby used for replicationValidate if required directories are created for RDS Oracle standbyValidate if Primary Key or Unique Index exists on target for Batch ApplyValidate if both Primary Key and Unique index exist on target for Batch ApplyValidate if unsupported HCC levels are used for Full LoadValidate if unsupported HCC levels are used for Full Load with CDCValidate if unsupported HCC compression used for CDCCDC Recommendation based on source compression methodCheck if batch apply is enabled and validate whether the table has more than 999 columnsCheck Transformation Rule for Digits RandomizeCheck Transformation Rule for Digits maskCheck Transformation Rule for Hashing maskVerify that Data Validation task settings and Data Masking Digit randomization are not enabled simultaneouslyVerify that Data Validation task settings and Data Masking Hashing mask are not enabled simultaneouslyVerify that Data Validation task settings and Data Masking Digit mask are not enabled simultaneouslyValidate that replication to a streaming target does not include LOBs or extended data type columnsValidate that CDC-only task is configured to use the OpenTransactionWindow endpoint settingValidate that at least one selected object exists in the source databaseValidate that target foreign key constraints are disabled for migrationValidate that the Oracle database and AWS DMS versions are compatibleValidate that secondary constraints and indexes (non-primary) are present in the source databaseValidate that session timeout settings (IDLE_TIME) are set to UNLIMITEDValidate that the AWS DMS user has all required permissions on the source databaseValidate that XMLTYPE or LOB columns exist when Oracle LogMiner is usedValidate that the target endpoint is not a read replicaValidate that the Oracle target does not have CONTEXT indexes when using direct path loadValidate that FailTasksOnLobTruncation is enabled when using limited LOB mode with existing LOB columnsValidate that EnableHomogenousPartitionOps endpoint setting is enabled
@@ -232,0 +233,8 @@ If you are using an AWS-managed Oracle database as a target for AWS DMS, use the
+  * Validate that the target endpoint is not a read replica
+
+  * Validate that the Oracle target does not have CONTEXT indexes when using direct path load
+
+  * Validate that FailTasksOnLobTruncation is enabled when using limited LOB mode with existing LOB columns
+
+  * Validate that EnableHomogenousPartitionOps endpoint setting is enabled
+
@@ -388 +396 @@ This premigration assessment validates whether supplemental logging is enabled f
-This premigration assessment checks for the presence of SecureFile LOBs in tables within the task scope and verifies their LOB settings. It's important to note that SecureFile LOBs are currently supported only during FULL LOB mode. Consider assigning LOB tables to a separate task to enhance performance, as running tasks in full LOB mode may result in slower performance. 
+This premigration assessment checks for the presence of SecureFile LOBs in tables within the task scope and verifies their LOB settings. Consider assigning LOB tables to a separate task to enhance performance, as running tasks in full LOB mode may result in slower performance. 
@@ -779,0 +788,30 @@ This premigration assessment warns that `XMLTYPE` or LOB columns exist in the so
+## Validate that the target endpoint is not a read replica
+
+**API key** : `all-check-target-read-replica`
+
+This premigration assessment verifies that the target endpoint is not configured as a read replica. AWS DMS requires write access to the target database and cannot replicate to read-only replicas.
+
+## Validate that the Oracle target does not have CONTEXT indexes when using direct path load
+
+**API key** : `oracle-check-direct-path-context-indexes`
+
+This premigration assessment validates whether target Oracle tables contain CONTEXT indexes. AWS DMS does not support CONTEXT indexes when using direct path in full-load mode. To avoid failure, disable direct path full-load mode or remove CONTEXT indexes before the load.
+
+For more information, see [Limitations on using Oracle as a source for AWS DMS](./CHAP_Source.Oracle.html#CHAP_Source.Oracle.Limitations).
+
+## Validate that `FailTasksOnLobTruncation` is enabled when using limited LOB mode with existing LOB columns
+
+**API key** : `oracle-pg-lobs-with-failtasksonlobtruncation`
+
+This premigration assessment validates whether the `FailTasksOnLobTruncation` extra connection attribute is set to true when LOB columns are present in selected tables and limited LOB mode is specified. This setting fails the task if any LOB data is truncated during migration, preventing silent data loss.
+
+For more information, see [Endpoint settings when using Oracle as a source for AWS DMS](./CHAP_Source.Oracle.html#CHAP_Source.Oracle.ConnectionAttrib).
+
+## Validate that `EnableHomogenousPartitionOps` endpoint setting is enabled
+
+**API key** : `oracle-homogenous-partition-ops`
+
+This premigration assessment validates that the `EnableHomogenousPartitionOps` endpoint setting is enabled for Oracle homogeneous migrations. This setting is required for AWS DMS to replicate Oracle partition and subpartition DDL operations.
+
+For more information, see [Limitations on using Oracle as a source for AWS DMS](./CHAP_Source.Oracle.html#CHAP_Source.Oracle.Limitations).
+