AWS dms documentation change
Summary
Added error resolution for 'Bad Envelope' CDC failures and minor text updates
Security assessment
Documents a workaround for transaction processing errors but does not address security vulnerabilities. The 'ignoreTxnCtxValidityCheck' parameter adjustment relates to data consistency rather than security controls.
Diff
diff --git a/dms/latest/userguide/CHAP_Troubleshooting.md b/dms/latest/userguide/CHAP_Troubleshooting.md index 62df443e8..2ece1ed98 100644 --- a//dms/latest/userguide/CHAP_Troubleshooting.md +++ b//dms/latest/userguide/CHAP_Troubleshooting.md @@ -929 +929 @@ Following, you can learn about troubleshooting issues specific to using AWS DMS - * Changes don't appear in your target + * Changes do not appear in your target @@ -932,0 +933,2 @@ Following, you can learn about troubleshooting issues specific to using AWS DMS + * Error : CDC task failed with a Bad Envelope, invalid data context/LCX code while processing a transaction + @@ -976 +978 @@ AWS DMS currently doesn't support SQL Server Express as a source or target. -### Changes don't appear in your target +### Changes do not appear in your target @@ -982 +984 @@ The SIMPLE recovery model logs the minimal information needed to allow users to -All operations are still logged. However, as soon as a checkpoint occurs the log is automatically truncated. This truncation means that the log becomes available for reuse and older log entries can be overwritten. When log entries are overwritten, changes can't be captured. This issue is why AWS DMS doesn't support the SIMPLE data recovery model. For information on other required prerequisites for using SQL Server as a source, see [Using a Microsoft SQL Server database as a source for AWS DMS](./CHAP_Source.SQLServer.html). +All operations are still logged. However, as soon as a checkpoint occurs the log is automatically truncated. This truncation means that the log becomes available for reuse and older log entries can be overwritten. When log entries are overwritten, changes can't be captured. This issue is why AWS DMS does not support the SIMPLE data recovery model. For information on other required prerequisites for using SQL Server as a source, see [Using a Microsoft SQL Server database as a source for AWS DMS](./CHAP_Source.SQLServer.html). @@ -1001 +1003,4 @@ AWS DMS expects that metadata to be the same for all raw partitions of the table - * If the table doesn't have a clustered index, add a clustered index to the table (you can drop it later if you want). + * If the table does not have a clustered index, add a clustered index to the table (you can drop it later if you want). + + + @@ -1002,0 +1008 @@ AWS DMS expects that metadata to be the same for all raw partitions of the table +### Error : CDC task failed with a Bad Envelope, invalid data context/LCX code while processing a transaction @@ -1003,0 +1010 @@ AWS DMS expects that metadata to be the same for all raw partitions of the table +The 'Bad Envelope' error occurs when AWS DMS is unable to validate specific event types in CDC phase replication during the validation process. This error can commonly occur when resuming tasks from a specific timestamp that falls in the middle of a transaction. In such cases, the task might read a commit event without finding its corresponding 'start transaction' event, leading to an invalid transaction context, and triggering the 'Bad Envelope' error. @@ -1004,0 +1012 @@ AWS DMS expects that metadata to be the same for all raw partitions of the table +To resolve this issue, you must modify the SQL Server source endpoint configuration by setting the `ignoreTxnCtxValidityCheck` parameter to `true` in the Extra Connection Attribute section, before resuming the task. If the error persists after implementing this solution, submit an AWS [support ticket](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html).