AWS dms documentation change
Summary
Restructured documentation for Oracle to MySQL conversion settings, adding detailed configuration options for ROWID emulation, function conversions (TO_CHAR/TO_DATE/TO_NUMBER), and time zone handling. Included API/CLI parameter names, type definitions, default values, and an example configuration.
Security assessment
Changes focus on functional conversion settings (ROWID emulation, function behavior, time zones) without mentioning vulnerabilities, security patches, or access controls. No evidence of addressing security incidents or weaknesses.
Diff
diff --git a/dms/latest/userguide/schema-conversion-oracle-mysql.md b/dms/latest/userguide/schema-conversion-oracle-mysql.md index 338ac837f..9079614bc 100644 --- a//dms/latest/userguide/schema-conversion-oracle-mysql.md +++ b//dms/latest/userguide/schema-conversion-oracle-mysql.md @@ -7 +7 @@ -# Understanding Oracle to MySQL conversion settings +Example: Configure Oracle to MySQL settings @@ -9 +9 @@ -Oracle to MySQL conversion settings in DMS Schema Conversion include the following: +# Oracle to MySQL conversion settings @@ -11 +11 @@ Oracle to MySQL conversion settings in DMS Schema Conversion include the followi - * Your source Oracle database can use the `ROWID` pseudocolumn. MySQL doesn't support similar functionality. DMS Schema Conversion can emulate the `ROWID` pseudocolumn in the converted code. To do so, turn on the **Generate row ID** option. +The following settings apply when the source is Oracle and the target is Amazon RDS for MySQL or Amazon Aurora MySQL. You can configure these settings using the AWS Management Console or the [ModifyConversionConfiguration](https://docs.aws.amazon.com/dms/latest/APIReference/API_ModifyConversionConfiguration.html) API operation. @@ -13 +13 @@ Oracle to MySQL conversion settings in DMS Schema Conversion include the followi -If your source Oracle code doesn't use the `ROWID` pseudocolumn, turn off the **Generate row ID** option. In this case, the converted code works faster. +This topic covers settings specific to the Oracle to MySQL conversion path. In addition to these settings, DMS Schema Conversion provides settings that apply to all source and target pairs, such as the severity level for action-item comments in converted SQL and the option to use generative AI for conversion. For those settings, see [Common conversion settings](./schema-conversion-settings.html#schema-conversion-settings-common). @@ -15 +15 @@ If your source Oracle code doesn't use the `ROWID` pseudocolumn, turn off the ** - * Your source Oracle code can include the `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions with parameters that MySQL doesn't support. By default, DMS Schema Conversion emulates the usage of these parameters in the converted code. +When you use the API or AWS CLI, specify conversion path settings under the section name `ORACLE_TO_MYSQL`. To confirm the section names that your project uses, call [DescribeConversionConfiguration](https://docs.aws.amazon.com/dms/latest/APIReference/API_DescribeConversionConfiguration.html) first and update only the sections present in the response. @@ -17 +17 @@ If your source Oracle code doesn't use the `ROWID` pseudocolumn, turn off the ** -You can use native MySQL `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions when your source Oracle code lacks parameters that are unsupported by MySQL. In this case, the converted code works faster. To do so, select the following values: +Each setting shows the AWS Management Console label followed by the API and AWS CLI parameter name in parentheses. Use the parameter name when configuring settings with the API or AWS CLI. @@ -19 +19 @@ You can use native MySQL `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions when yo - * **Use a native MySQL TO_CHAR function** +**Generate row id** (`GenerateRowId`) @@ -21 +20,0 @@ You can use native MySQL `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions when yo - * **Use a native MySQL TO_DATE function** @@ -23 +22 @@ You can use native MySQL `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions when yo - * **Use a native MySQL TO_NUMBER function** +Your source Oracle database can use the `ROWID` pseudocolumn. MySQL doesn't support similar functionality. This setting specifies whether DMS Schema Conversion emulates the `ROWID` pseudocolumn in the converted code. @@ -25 +24,4 @@ You can use native MySQL `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions when yo - * Your database and applications can run in different time zones. By default, DMS Schema Conversion emulates time zones in the converted code. However, you don't need this emulation when your database and applications use the same time zone. In this case, select **Improve the performance of the converted code where the database and applications use the same time zone**. +Console label | API/CLI value | Behavior +---|---|--- +**Don't generate** | `false` | DMS Schema Conversion doesn't emulate the `ROWID` pseudocolumn and leaves references as action items. Use this when your source Oracle code doesn't use `ROWID`. The converted code runs faster. +**Use the bigint data type to emulate the ROWID pseudocolumn** | `true` | DMS Schema Conversion emulates the `ROWID` pseudocolumn in the converted code by using the `bigint` data type. @@ -26,0 +29 @@ You can use native MySQL `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions when yo +**Type:** Boolean (`true` | `false`) @@ -27,0 +31 @@ You can use native MySQL `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions when yo +**Default:** `false` @@ -28,0 +33,84 @@ You can use native MySQL `TO_CHAR`, `TO_DATE`, and `TO_NUMBER` functions when yo +###### Note + +For the Oracle to MySQL conversion path, `GenerateRowId` is a Boolean (`true` | `false`) and emulates the `ROWID` pseudocolumn by using the `bigint` data type only. For the Oracle to PostgreSQL conversion path, the same setting is a string enumeration that also offers a `character varying` emulation option (`GENERATE_AS_CHARACTER_DOMAIN_TYPE`). For more information, see [Oracle to PostgreSQL conversion settings](./schema-conversion-oracle-postgresql.html). + +###### Function conversion settings + +By default, DMS Schema Conversion emulates Oracle conversion functions in the converted code so that the result matches the Oracle behavior. If your source code doesn't rely on Oracle-specific formatting, you can convert these functions to the native MySQL equivalents instead. Native functions run faster, so set these options to `true` only after you verify that your usage is compatible with MySQL. + +**Use a native MySQL TO_CHAR function** (`ToCharFunctionOracle`) + + +Specifies whether DMS Schema Conversion converts Oracle `TO_CHAR` function calls to the native MySQL function instead of emulating the Oracle-specific formatting. + + * `false` — DMS Schema Conversion emulates the Oracle-specific formatting of `TO_CHAR` in the converted code. + + * `true` — Calls are converted to the native MySQL `TO_CHAR` function. Use this when your source code doesn't use Oracle-specific format strings. + + + + +**Type:** Boolean (`true` | `false`) + +**Default:** `false` + +**Use a native MySQL TO_DATE function** (`ToDateFunctionOracle`) + + +Specifies whether DMS Schema Conversion converts Oracle `TO_DATE` function calls to the native MySQL function instead of emulating the Oracle-specific formatting. + + * `false` — DMS Schema Conversion emulates the Oracle-specific formatting of `TO_DATE` in the converted code. + + * `true` — Calls are converted to the native MySQL `TO_DATE` function. Use this when your source code doesn't use Oracle-specific format strings. + + + + +**Type:** Boolean (`true` | `false`) + +**Default:** `false` + +**Use a native MySQL TO_NUMBER function** (`ToNumber`) + + +Specifies whether DMS Schema Conversion converts Oracle `TO_NUMBER` function calls to the native MySQL function instead of emulating the Oracle-specific formatting. + + * `false` — DMS Schema Conversion emulates the Oracle-specific formatting of `TO_NUMBER` in the converted code. + + * `true` — Calls are converted to the native MySQL `TO_NUMBER` function. Use this when your source code doesn't use Oracle-specific format strings. + + + + +**Type:** Boolean (`true` | `false`) + +**Default:** `false` + +**Improve the performance of the converted code where the database and applications use the same time zone** (`ToTimeZone`) + + +Specifies whether DMS Schema Conversion emulates time zones in the converted code. + + * `true` — DMS Schema Conversion doesn't emulate time zones. Use this when your database and applications use the same time zone. The converted code runs faster. + + * `false` — DMS Schema Conversion emulates time zones in the converted code. + + + + +**Type:** Boolean (`true` | `false`) + +**Default:** `false` + +## Example: Configure Oracle to MySQL settings + +The following example converts Oracle conversion functions to their native MySQL equivalents for the `ORACLE_TO_MYSQL` section. + + + { + "ORACLE_TO_MYSQL": { + "ToCharFunctionOracle": true, + "ToDateFunctionOracle": true, + "ToNumber": true + } + }