AWS dms documentation change
Summary
Updated documentation for Db2 LUW source endpoints with revised ECA (Extra Connection Attribute) handling: corrected parameter casing (CurrentLSN→CurrentLsn), separated endpoint settings from ECAs, added explicit syntax examples, and restructured StartFromContext configuration guidance.
Security assessment
Changes focus on parameter naming consistency (case sensitivity) and documentation structure improvements. No evidence of addressing vulnerabilities or security incidents. Timeout parameters (ConnectionTimeout/executeTimeout) are standard configuration settings rather than new security features.
Diff
diff --git a/dms/latest/userguide/CHAP_Source.DB2.md b/dms/latest/userguide/CHAP_Source.DB2.md index 197ed1d72..7dc36c9bc 100644 --- a//dms/latest/userguide/CHAP_Source.DB2.md +++ b//dms/latest/userguide/CHAP_Source.DB2.md @@ -5 +5 @@ -Prerequisites when using Db2 LUW as a sourceLimitations when using Db2 LUW as a sourceEndpoint settingsSource data types for Db2 LUW +Prerequisites when using Db2 LUW as a sourceLimitations when using Db2 LUW as a sourceEndpoint settingsEndpoint ECAsSource data types for Db2 LUW @@ -39 +39 @@ For full-load only tasks, the DMS user account needs DATAACCESS permission. - * When using IBM DB2 for LUW version 9.7 as a source, set the extra connection attribute (ECA), `CurrentLSN` as follows: + * When using IBM DB2 for LUW version 9.7 as a source, set the extra connection attribute (ECA), `CurrentLsn` as follows: @@ -41 +41 @@ For full-load only tasks, the DMS user account needs DATAACCESS permission. -`CurrentLSN=`LSN`` where ``LSN`` specifies a log sequence number (LSN) where you want the replication to start. Or, `CurrentLSN=`scan``. +`CurrentLsn=`LSN`` where ``LSN`` specifies a log sequence number (LSN) where you want the replication to start. Or, `CurrentLsn=`scan``. @@ -108 +108 @@ When using ongoing replication (CDC), the following limitations apply: - * When migrating from a DPF environment, we recommend first running a Full Load task without cached events, and then running CDC-only tasks. We recommend running one task per Db2 node, starting from the Full Load start timestamp or LRI (log record identifier) you set using the `StartFromContext` endpoint setting. For information about determining your replication start point, see [ Finding the LSN or LRI value for replication start ](https://www.ibm.com/support/pages/db2-finding-lsn-or-lri-value-replication-start) in the _IBM Support documentation_. + * When migrating from a DPF environment, we recommend first running a Full Load task without cached events, and then running CDC-only tasks. We recommend running one task per Db2 node, starting from the Full Load start timestamp or LRI (log record identifier) you set using the `StartFromContext` endpoint extra connection attribute. For information about determining your replication start point, see [ Finding the LSN or LRI value for replication start ](https://www.ibm.com/support/pages/db2-finding-lsn-or-lri-value-replication-start) in the _IBM Support documentation_. @@ -110 +110 @@ When using ongoing replication (CDC), the following limitations apply: - * For ongoing replication (CDC), if you plan to start replication from a specific timestamp, you must set the `StartFromContext` connection attribute to the required timestamp. + * For ongoing replication (CDC), if you plan to start replication from a specific timestamp, you must set the `StartFromContext` extra connection attribute to the required timestamp. @@ -123 +123,5 @@ When using ongoing replication (CDC), the following limitations apply: -You can use endpoint settings to configure your Db2 LUW source database similar to using extra connection attributes. You specify the settings when you create the source endpoint using the AWS DMS console, or by using the `create-endpoint` command in the [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/dms/index.html), with the `--ibm-db2-settings '{"`EndpointSetting"`: `"value"`, `...`}'` JSON syntax. +You can specify the settings when you create the source endpoint using the AWS DMS console, or by using the `create-endpoint` command in the [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/dms/create-endpoint.html), with the + +`--ibm-db2-settings `'{"EndpointSetting1": "value1","EndpointSetting2": "value2"}'`` + +JSON syntax. @@ -127 +131 @@ The following table shows the endpoint settings that you can use with Db2 LUW as -Name | Description +Setting Name | Description @@ -129,2 +133 @@ Name | Description -`CurrentLSN` | For ongoing replication (CDC), use `CurrentLSN` to specify a log sequence number (LSN) where you want the replication to start. -`ConnectionTimeout` | Use this extra connection attribute (ECA) to set the endpoint connection timeout for the Db2 LUW endpoint, in seconds. The default value is 10 seconds. ECA Example: `ConnectionTimeout=30`. +`CurrentLsn` | For ongoing replication (CDC), use `CurrentLsn` to specify a log sequence number (LSN) where you want the replication to start. @@ -133,3 +135,0 @@ Name | Description -`StartFromContext` | For ongoing replication (CDC), use `StartFromContext` to specify a log's lower limit from where to start the replication. `StartFromContext` accepts different forms of values. Valid values include: - - * `timestamp` (UTC). For example: @@ -137 +137 @@ Name | Description - '{"StartFromContext": "timestamp:2021-09-21T13:00:00"}' +## Extra Connection Attributes (ECAs) when using Db2 LUW as a source for AWS DMS @@ -138,0 +139 @@ Name | Description +You can specify the Extra Connection Attributes (ECAs) when you create the source endpoint using the AWS DMS console, or by using the `create-endpoint` command in the [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/dms/create-endpoint.html), with the @@ -139,0 +141 @@ Name | Description +`--extra-connection-attributes `'ECAname1=value1;ECAname2=value2;'`` @@ -140,0 +143 @@ Name | Description +The following table shows the ECAs that you can use with Db2 LUW as a source. @@ -142 +145,5 @@ Name | Description - * `NOW` For IBM DB2 LUW version 10.5 and higher, NOW combined with CurrentLSN: scan, starts the task from the latest LSO. For example: +Attribute Name | Description +---|--- +`ConnectionTimeout` | Use this ECA to set the endpoint connection timeout for the Db2 LUW endpoint, in seconds. The default value is 10 seconds. Example: `ConnectionTimeout=30;` +`executeTimeout` | Extra connection attribute which sets the statement (query) timeout for the DB2 LUW endpoint, in seconds. The default value is 60 seconds. Example: `executeTimeout=120;` +`StartFromContext` | For ongoing replication (CDC), use `StartFromContext` to specify a log's lower limit from where to start the replication. `StartFromContext` accepts different forms of values. Valid values include: @@ -144 +151 @@ Name | Description - '{"CurrentLSN": "scan", "StartFromContext": "NOW"}' + * `timestamp` (UTC). Example: `StartFromContext=timestamp:2026-02-23T13:00:00;` @@ -147,0 +155 @@ Name | Description + * `NOW` For IBM DB2 LUW version 10.5 and higher, NOW combined with `'{"CurrentLsn": "scan"}'` endpoint setting, starts the task from the latest Log Sequence Offset (LSO). Example: `StartFromContext=NOW;` @@ -149 +156,0 @@ Name | Description - * A specific LRI. For example: @@ -151 +157,0 @@ Name | Description - '{"StartFromContext": "0100000000000022CC000000000004FB13"}' @@ -152,0 +159 @@ Name | Description + * A specific Log Record Identifier (LRI). Example: `StartFromContext=0100000000000022CC000000000004FB13;` @@ -170,2 +176,0 @@ In that output, the log file is S0000002.LOG and the **StartFromContext** LRI va -`executeTimeout` | Extra connection attribute which sets the statement (query) timeout for the DB2 LUW endpoint, in seconds. The default value is 60 seconds. ECA Example: `executeTimeout=120;` -