AWS dms documentation change
Summary
Multiple grammatical corrections changing 'doesn't' to 'does not' throughout the document. Updated TDE (Transparent Data Encryption) support notes and clarified limitations around encryption, CDC, and database version compatibility.
Security assessment
Changes are primarily grammatical fixes and clarifications of existing limitations. While TDE-related sections discuss encryption support, the updates do not introduce new security features or address specific vulnerabilities. The corrections to TDE credential behavior describe existing functionality rather than patching a security issue.
Diff
diff --git a/dms/latest/userguide/CHAP_Source.Oracle.md b/dms/latest/userguide/CHAP_Source.Oracle.md index 3bfe47d96..da4f3b564 100644 --- a//dms/latest/userguide/CHAP_Source.Oracle.md +++ b//dms/latest/userguide/CHAP_Source.Oracle.md @@ -88 +88 @@ Supports Oracle table clusters | Yes | No -Supports all types of Oracle Hybrid Columnar Compression (HCC) | Yes | Partially Binary Reader doesn't support QUERY LOW for tasks with CDC. All other HCC types are fully supported. +Supports all types of Oracle Hybrid Columnar Compression (HCC) | Yes | Partially Binary Reader does not support QUERY LOW for tasks with CDC. All other HCC types are fully supported. @@ -91 +91 @@ Supports `UPDATE` statements that affect only LOB columns | No | Yes -Supports Oracle transparent data encryption (TDE) | Partially When using Oracle LogMiner, AWS DMS doesn't support TDE encryption on column level for Amazon RDS for Oracle. | Partially Binary Reader supports TDE only for self-managed Oracle databases. +Supports Oracle transparent data encryption (TDE) | Partially When using Oracle LogMiner, AWS DMS does not support TDE encryption on column level for Amazon RDS for Oracle. | Partially Binary Reader supports TDE only for self-managed Oracle databases. @@ -100 +100 @@ By default, AWS DMS uses Oracle LogMiner for (CDC). -AWS DMS supports transparent data encryption (TDE) methods when working with an Oracle source database. If the TDE credentials you specify are incorrect, the AWS DMS migration task doesn't fail, which can impact ongoing replication of encrypted tables. For more information about specifying TDE credentials, see Supported encryption methods for using Oracle as a source for AWS DMS. +AWS DMS supports transparent data encryption (TDE) methods when working with an Oracle source database. If the TDE credentials you specify are incorrect, the AWS DMS migration task does not fail, which can impact ongoing replication of encrypted tables. For more information about specifying TDE credentials, see Supported encryption methods for using Oracle as a source for AWS DMS. @@ -104 +104 @@ The main advantages of using LogMiner with AWS DMS include the following: - * LogMiner supports most Oracle options, such as encryption options and compression options. Binary Reader doesn't support all Oracle options, particularly compression and most options for encryption. + * LogMiner supports most Oracle options, such as encryption options and compression options. Binary Reader does not support all Oracle options, particularly compression and most options for encryption. @@ -108 +108 @@ The main advantages of using LogMiner with AWS DMS include the following: - * LogMiner supports table clusters for use by AWS DMS. Binary Reader doesn't. + * LogMiner supports table clusters for use by AWS DMS. Binary Reader does not. @@ -119 +119 @@ The main advantages of using Binary Reader with AWS DMS include the following: - * Binary Reader supports CDC for LOBs in Oracle version 12c. LogMiner doesn't. + * Binary Reader supports CDC for LOBs in Oracle version 12c. LogMiner does not. @@ -192 +192 @@ If you haven't already done so, configure the task to use LogMiner or Binary Rea -Configure Oracle Standby as a source for CDC. | AWS DMS doesn't support Oracle Standby as a source. | See Using a self-managed Oracle Standby as a source with Binary Reader for CDC in AWS DMS. +Configure Oracle Standby as a source for CDC. | AWS DMS does not support Oracle Standby as a source. | See Using a self-managed Oracle Standby as a source with Binary Reader for CDC in AWS DMS. @@ -202 +202 @@ If you haven't already done so, configure the task to use LogMiner or Binary Rea -Configure Oracle Standby as a source for CDC. | AWS DMS doesn't support Oracle Standby as a source. | For more information, see Using an Amazon RDS Oracle Standby (read replica) as a source with Binary Reader for CDC in AWS DMS. +Configure Oracle Standby as a source for CDC. | AWS DMS does not support Oracle Standby as a source. | For more information, see Using an Amazon RDS Oracle Standby (read replica) as a source with Binary Reader for CDC in AWS DMS. @@ -344 +344 @@ Run a query like the following to verify that the current version of the Oracle -Here, `name`, `value`, and `description` are columns somewhere in the database that are being queried based on the value of `name`. If this query runs without error, AWS DMS supports the current version of the database and you can continue with the migration. If the query raises an error, AWS DMS doesn't support the current version of the database. To proceed with migration, first convert the Oracle database to an version supported by AWS DMS. +Here, `name`, `value`, and `description` are columns somewhere in the database that are being queried based on the value of `name`. If this query runs without error, AWS DMS supports the current version of the database and you can continue with the migration. If the query raises an error, AWS DMS does not support the current version of the database. To proceed with migration, first convert the Oracle database to an version supported by AWS DMS. @@ -366 +366 @@ You can disable the default `PRIMARY KEY` supplemental logging added by AWS DMS -Make sure to turn on supplemental logging if your replication task updates a table using a `WHERE` clause that doesn't reference a primary key column. +Make sure to turn on supplemental logging if your replication task updates a table using a `WHERE` clause that does not reference a primary key column. @@ -395 +395 @@ Consider the following: -Using `SUPPLEMENTAL LOG DATA (UNIQUE INDEX) COLUMNS` doesn't add the unique index columns to the log. +Using `SUPPLEMENTAL LOG DATA (UNIQUE INDEX) COLUMNS` does not add the unique index columns to the log. @@ -399 +399 @@ Using `SUPPLEMENTAL LOG DATA (UNIQUE INDEX) COLUMNS` doesn't add the unique inde -Using `SUPPLEMENTAL LOG DATA (UNIQUE INDEX) COLUMNS` doesn't add the unique index columns to the log. +Using `SUPPLEMENTAL LOG DATA (UNIQUE INDEX) COLUMNS` does not add the unique index columns to the log. @@ -447 +447 @@ To access the redo logs using the AWS DMS Binary Reader, grant the following pri - GRANT CREATE ANY DIRECTORY to dms_user; -– Grant this privilege to allow AWS DMS to use Oracle BFILE read file access in certain cases. This access is required when the replication instance doesn't have file-level access to the redo logs and the redo logs are on non-ASM storage. + GRANT CREATE ANY DIRECTORY to dms_user; -– Grant this privilege to allow AWS DMS to use Oracle BFILE read file access in certain cases. This access is required when the replication instance does not have file-level access to the redo logs and the redo logs are on non-ASM storage. @@ -451 +451 @@ To access the redo logs using the AWS DMS Binary Reader, grant the following pri -Binary Reader works with Oracle file features that include Oracle directories. Each Oracle directory object includes the name of the folder containing the redo log files to process. These Oracle directories aren't represented at the file system level. Instead, they are logical directories that are created at the Oracle database level. You can view them in the Oracle `ALL_DIRECTORIES` view. +Binary Reader works with Oracle file features that include Oracle directories. Each Oracle directory object includes the name of the folder containing the redo log files to process. These Oracle directories are not represented at the file system level. Instead, they are logical directories that are created at the Oracle database level. You can view them in the Oracle `ALL_DIRECTORIES` view. @@ -459 +459 @@ If the Oracle source endpoint is in Active Dataguard Standby (ADG), see the [How -AWS DMS CDC doesn't support Active Dataguard Standby that is not configured to use automatic redo transport service. +AWS DMS CDC does not support Active Dataguard Standby that is not configured to use automatic redo transport service. @@ -461 +461 @@ AWS DMS CDC doesn't support Active Dataguard Standby that is not configured to u -In some cases, you might use Oracle Managed Files (OMF) for storing the logs. Or your source endpoint is in ADG and thus you can't grant the CREATE ANY DIRECTORY privilege. In these cases, manually create the directories with all the possible log locations before starting the AWS DMS replication task. If AWS DMS doesn't find a precreated directory that it expects, the task stops. Also, AWS DMS doesn't delete the entries it has created in the `ALL_DIRECTORIES` view, so manually delete them. +In some cases, you might use Oracle Managed Files (OMF) for storing the logs. Or your source endpoint is in ADG and thus you can't grant the CREATE ANY DIRECTORY privilege. In these cases, manually create the directories with all the possible log locations before starting the AWS DMS replication task. If AWS DMS does not find a precreated directory that it expects, the task stops. Also, AWS DMS does not delete the entries it has created in the `ALL_DIRECTORIES` view, so manually delete them. @@ -599 +599 @@ The following limitations apply when replicating data from an Oracle source data - * DMS doesn't support using Oracle LogMiner to access the redo logs. + * DMS does not support using Oracle LogMiner to access the redo logs. @@ -601 +601 @@ The following limitations apply when replicating data from an Oracle source data - * DMS doesn't support Autonomous DB. + * DMS does not support Autonomous DB. @@ -870 +870 @@ The following limitations apply when using an Oracle database as a source for AW - * AWS DMS doesn't support long object names (over 30 bytes). + * AWS DMS does not support long object names (over 30 bytes). @@ -872 +872 @@ The following limitations apply when using an Oracle database as a source for AW - * AWS DMS doesn't support function-based indexes. + * AWS DMS does not support function-based indexes. @@ -880 +880 @@ The following limitations apply when using an Oracle database as a source for AW - * AWS DMS doesn't support the multi-tenant container root database (CDB$ROOT). It does support a PDB using the Binary Reader. + * AWS DMS does not support the multi-tenant container root database (CDB$ROOT). It does support a PDB using the Binary Reader. @@ -882 +882 @@ The following limitations apply when using an Oracle database as a source for AW - * AWS DMS doesn't support deferred constraints. + * AWS DMS does not support deferred constraints. @@ -888 +888 @@ The following limitations apply when using an Oracle database as a source for AW - * AWS DMS doesn't replicate results of the DDL statement `ALTER TABLE ADD `column` `data_type` DEFAULT `default_value``. Instead of replicating ``default_value`` to the target, it sets the new column to `NULL`. + * AWS DMS does not replicate results of the DDL statement `ALTER TABLE ADD `column` `data_type` DEFAULT `default_value``. Instead of replicating ``default_value`` to the target, it sets the new column to `NULL`. @@ -898 +898 @@ The following limitations apply when using an Oracle database as a source for AW -For more information about `enableHomogenousPartitionOps`, see Endpoint settings when using Oracle as a source for AWS DMS. Also, note that on FULL+CDC tasks, DMS doesn't replicate data changes captured as part of the cached changes. In that use case, recreate the table structure on the Oracle target and reload the tables in question. +For more information about `enableHomogenousPartitionOps`, see Endpoint settings when using Oracle as a source for AWS DMS. Also, note that on FULL+CDC tasks, DMS does not replicate data changes captured as part of the cached changes. In that use case, recreate the table structure on the Oracle target and reload the tables in question. @@ -902 +902 @@ Prior to AWS DMS version 3.4.7: -DMS doesn't replicate data changes that result from partition or subpartition operations (`ADD`, `DROP`, `EXCHANGE`, and `TRUNCATE`). Such updates might cause the following errors during replication: +DMS does not replicate data changes that result from partition or subpartition operations (`ADD`, `DROP`, `EXCHANGE`, and `TRUNCATE`). Such updates might cause the following errors during replication: @@ -914 +914 @@ To replicate changes that result from partition or subpartition operations, relo - * AWS DMS doesn't capture changes made by the Oracle `DBMS_REDEFINITION` package, for example the table metadata and the `OBJECT_ID` field. + * AWS DMS does not capture changes made by the Oracle `DBMS_REDEFINITION` package, for example the table metadata and the `OBJECT_ID` field. @@ -920 +920 @@ To replicate changes that result from partition or subpartition operations, relo - * During change data capture (CDC), AWS DMS doesn't support batch updates to numeric columns defined as a primary key. + * During change data capture (CDC), AWS DMS does not support batch updates to numeric columns defined as a primary key. @@ -922 +922 @@ To replicate changes that result from partition or subpartition operations, relo - * AWS DMS doesn't support certain `UPDATE` commands. The following example is an unsupported `UPDATE` command. + * AWS DMS does not support certain `UPDATE` commands. The following example is an unsupported `UPDATE` command. @@ -928 +928 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't support full LOB mode for loading LONG and LONG RAW columns. Instead, you can use limited LOB mode for migrating these datatypes to an Oracle target. In limited LOB mode, AWS DMS truncates any data to 64 KB that you set to LONG or LONG RAW columns longer than 64 KB. + * AWS DMS does not support full LOB mode for loading LONG and LONG RAW columns. Instead, you can use limited LOB mode for migrating these datatypes to an Oracle target. In limited LOB mode, AWS DMS truncates any data to 64 KB that you set to LONG or LONG RAW columns longer than 64 KB. @@ -930 +930 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't support full LOB mode for loading XMLTYPE columns. Instead, you can use limited LOB mode for migrating XMLTYPE columns to an Oracle target. In limited LOB mode, DMS truncates any data larger than the user defined 'Maximum LOB size' variable. The maximum recommended value for 'Maximum LOB size' is 100MB. + * AWS DMS does not support full LOB mode for loading XMLTYPE columns. Instead, you can use limited LOB mode for migrating XMLTYPE columns to an Oracle target. In limited LOB mode, DMS truncates any data larger than the user defined 'Maximum LOB size' variable. The maximum recommended value for 'Maximum LOB size' is 100MB. @@ -932 +932 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't replicate tables whose names contain apostrophes. + * AWS DMS does not replicate tables whose names contain apostrophes. @@ -934 +934 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS supports CDC from materialized views. But DMS doesn't support CDC from any other views. + * AWS DMS supports CDC from materialized views. But DMS does not support CDC from any other views. @@ -936 +936 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't support CDC for index-organized tables with an overflow segment. + * AWS DMS does not support CDC for index-organized tables with an overflow segment. @@ -938 +938 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't support the `Drop Partition` operation for tables partitioned by reference with `enableHomogenousPartitionOps` set to `true`. + * AWS DMS does not support the `Drop Partition` operation for tables partitioned by reference with `enableHomogenousPartitionOps` set to `true`. @@ -942 +942 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * For Oracle 12 only, AWS DMS doesn't replicate any changes to LOB columns. + * For Oracle 12 only, AWS DMS does not replicate any changes to LOB columns. @@ -944 +944 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * For all Oracle versions, AWS DMS doesn't replicate the result of `UPDATE` operations on `XMLTYPE` and LOB columns. + * For all Oracle versions, AWS DMS does not replicate the result of `UPDATE` operations on `XMLTYPE` and LOB columns. @@ -946 +946 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't support XA transactions in replication while using Oracle LogMiner. + * AWS DMS does not support XA transactions in replication while using Oracle LogMiner. @@ -948 +948 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * Oracle LogMiner doesn't support connections to a pluggable database (PDB). To connect to a PDB, access the redo logs using Binary Reader. + * Oracle LogMiner does not support connections to a pluggable database (PDB). To connect to a PDB, access the redo logs using Binary Reader. @@ -954 +954 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * It doesn't support table clusters. + * It does not support table clusters. @@ -958 +958 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * It doesn't support changes to index-organized tables with key compression. + * It does not support changes to index-organized tables with key compression. @@ -960 +960 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * It doesn't support implementing online redo logs on raw devices. + * It does not support implementing online redo logs on raw devices. @@ -962 +962 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * Binary Reader supports TDE only for self-managed Oracle databases since RDS for Oracle doesn't support wallet password retrieval for TDE encryption keys. + * Binary Reader supports TDE only for self-managed Oracle databases since RDS for Oracle does not support wallet password retrieval for TDE encryption keys. @@ -964 +964 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't support connections to an Amazon RDS Oracle source using an Oracle Automatic Storage Management (ASM) proxy. + * AWS DMS does not support connections to an Amazon RDS Oracle source using an Oracle Automatic Storage Management (ASM) proxy. @@ -966 +966 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't support virtual columns. + * AWS DMS does not support virtual columns. @@ -968 +968 @@ Here, `TEST_TABLE` is the table name and `KEY` is a numeric column defined as a - * AWS DMS doesn't support the `ROWID` data type or materialized views based on a ROWID column. + * AWS DMS does not support the `ROWID` data type or materialized views based on a ROWID column. @@ -972 +972 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * AWS DMS doesn't load or capture global temporary tables. + * AWS DMS does not load or capture global temporary tables. @@ -978 +978 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * AWS DMS doesn't support use of multiple Oracle TDE encryption keys on the same source endpoint. Each endpoint can have only one attribute for TDE encryption Key Name "`securityDbEncryptionName`", and one TDE password for this key. + * AWS DMS does not support use of multiple Oracle TDE encryption keys on the same source endpoint. Each endpoint can have only one attribute for TDE encryption Key Name "`securityDbEncryptionName`", and one TDE password for this key. @@ -984 +984 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * When using Oracle 19.0 as source, AWS DMS doesn't support the following features: + * When using Oracle 19.0 as source, AWS DMS does not support the following features: @@ -992 +992 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * AWS DMS doesn't support migration of tables or views of type `BIN$` or `DR$`. + * AWS DMS does not support migration of tables or views of type `BIN$` or `DR$`. @@ -994 +994 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * Beginning with Oracle 18.x, AWS DMS doesn't support change data capture (CDC) from Oracle Express Edition (Oracle Database XE). + * Beginning with Oracle 18.x, AWS DMS does not support change data capture (CDC) from Oracle Express Edition (Oracle Database XE). @@ -998 +998 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * AWS DMS doesn't support replication from application containers. + * AWS DMS does not support replication from application containers. @@ -1000 +1000 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * AWS DMS doesn't support performing Oracle Flashback Database and restore points, as these operations affect the consistency of Oracle Redo Log files. + * AWS DMS does not support performing Oracle Flashback Database and restore points, as these operations affect the consistency of Oracle Redo Log files. @@ -1002 +1002 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * Direct-load `INSERT` procedure with the parallel execution option isn't supported in the following cases: + * Prior to AWS DMS version 3.5.3, Direct-load `INSERT` procedure with the parallel execution option is not supported in the following cases: @@ -1014 +1014 @@ AWS DMS has partial support for Oracle Materialized Views. For full-loads, DMS c - * AWS DMS doesn't migrate data from invisible columns in your source database. To include these columns in your migration scope, use the `ALTER TABLE` statement to make these columns visible. + * AWS DMS does not migrate data from invisible columns in your source database. To include these columns in your migration scope, use the `ALTER TABLE` statement to make these columns visible. @@ -1432 +1432 @@ Specify the password values in this order regardless of your Oracle database con -If the TDE credentials you specify are incorrect, the AWS DMS migration task doesn't fail. However, the task also doesn't read or apply ongoing replication changes to the target database. After starting the task, monitor **Table statistics** on the console migration task page to make sure changes are replicated. +If the TDE credentials you specify are incorrect, the AWS DMS migration task does not fail. However, the task also does not read or apply ongoing replication changes to the target database. After starting the task, monitor **Table statistics** on the console migration task page to make sure changes are replicated. @@ -1505 +1505 @@ AWS DMS has the following limitations in its support of Oracle nested tables as - * AWS DMS table mapping doesn't check that both the parent and child table or tables are selected for replication. That is, it's possible to select a parent table without a child or a child table without a parent. + * AWS DMS table mapping does not check that both the parent and child table or tables are selected for replication. That is, it's possible to select a parent table without a child or a child table without a parent. @@ -1682,2 +1682,2 @@ NCLOB | NCLOB To use this data type with AWS DMS, you must enable the use of NC -LONG | CLOB The LONG data type isn't supported in batch-optimized apply mode (TurboStream CDC mode). To use this data type with AWS DMS, enable the use of LOBs for a specific task. During CDC or full load, AWS DMS supports LOB data types only in tables that have a primary key. Also, AWS DMS doesn't support full LOB mode for loading LONG columns. Instead, you can use limited LOB mode for migrating LONG columns to an Oracle target. In limited LOB mode, AWS DMS truncates any data to 64 KB that you set to LONG columns longer than 64 KB. For more information about LOB support in AWS DMS, see [Setting LOB support for source databases in an AWS DMS task](./CHAP_Tasks.LOBSupport.html) -LONG RAW | BLOB The LONG RAW data type isn't supported in batch-optimized apply mode (TurboStream CDC mode). To use this data type with AWS DMS, enable the use of LOBs for a specific task. During CDC or full load, AWS DMS supports LOB data types only in tables that have a primary key. Also, AWS DMS doesn't support full LOB mode for loading LONG RAW columns. Instead, you can use limited LOB mode for migrating LONG RAW columns to an Oracle target. In limited LOB mode, AWS DMS truncates any data to 64 KB that you set to LONG RAW columns longer than 64 KB. For more information about LOB support in AWS DMS, see [Setting LOB support for source databases in an AWS DMS task](./CHAP_Tasks.LOBSupport.html) +LONG | CLOB The LONG data type isn't supported in batch-optimized apply mode (TurboStream CDC mode). To use this data type with AWS DMS, enable the use of LOBs for a specific task. During CDC or full load, AWS DMS supports LOB data types only in tables that have a primary key. Also, AWS DMS does not support full LOB mode for loading LONG columns. Instead, you can use limited LOB mode for migrating LONG columns to an Oracle target. In limited LOB mode, AWS DMS truncates any data to 64 KB that you set to LONG columns longer than 64 KB. For more information about LOB support in AWS DMS, see [Setting LOB support for source databases in an AWS DMS task](./CHAP_Tasks.LOBSupport.html) +LONG RAW | BLOB The LONG RAW data type isn't supported in batch-optimized apply mode (TurboStream CDC mode). To use this data type with AWS DMS, enable the use of LOBs for a specific task. During CDC or full load, AWS DMS supports LOB data types only in tables that have a primary key. Also, AWS DMS does not support full LOB mode for loading LONG RAW columns. Instead, you can use limited LOB mode for migrating LONG RAW columns to an Oracle target. In limited LOB mode, AWS DMS truncates any data to 64 KB that you set to LONG RAW columns longer than 64 KB. For more information about LOB support in AWS DMS, see [Setting LOB support for source databases in an AWS DMS task](./CHAP_Tasks.LOBSupport.html) @@ -1687 +1687 @@ SDO_GEOMETRY | BLOB (when an Oracle to Oracle migration)CLOB (when an Oracle to -Oracle tables used as a source with columns of the following data types aren't supported and can't be replicated. Replicating columns with these data types result in a null column. +Oracle tables used as a source with columns of the following data types are not supported and can't be replicated. Replicating columns with these data types result in a null column. @@ -1708 +1708 @@ Oracle tables used as a source with columns of the following data types aren't s -Virtual columns aren't supported. +Virtual columns are not supported. @@ -1724 +1724 @@ When you migrate Oracle spatial data types using AWS DMS, be aware of these cons - * AWS DMS supports Oracle Spatial Column migrations for Full LOB mode only. AWS DMS doesn't support Limited LOB or Inline LOB modes. For more information about LOB mode, see [Setting LOB support for source databases in an AWS DMS task](./CHAP_Tasks.LOBSupport.html). + * AWS DMS supports Oracle Spatial Column migrations for Full LOB mode only. AWS DMS does not support Limited LOB or Inline LOB modes. For more information about LOB mode, see [Setting LOB support for source databases in an AWS DMS task](./CHAP_Tasks.LOBSupport.html). @@ -1726 +1726 @@ When you migrate Oracle spatial data types using AWS DMS, be aware of these cons - * Because AWS DMS only supports Full LOB mode for migrating Oracle Spatial Columns, the columns' table needs a primary key and a unique key. If the table doesn't have a primary key and a unique key, the table is skipped from migration. + * Because AWS DMS only supports Full LOB mode for migrating Oracle Spatial Columns, the columns' table needs a primary key and a unique key. If the table does not have a primary key and a unique key, the table is skipped from migration.