What should the database administrator do to identify’ this issue in the MOST operationally efficient manner?
Export AWS DMS logs to Amazon CloudWatch and identify the DDL statement from the AWS Management Console
Turn on logging for the AWS DMS task by setting the TARGET_LOAD action with the level of severity set to LOGGER_SEVERITY_DETAILED_DEBUG
Turn on DDL activity tracing in the RDS for Oracle DB instance parameter group
Turn on logging for the AWS DMS task by setting the TARGET_APPLY action with the level of severity’ set to LOGGER_SEVERITY_DETAILED_DEBUG
Explanations:
AWS DMS logs can be exported to CloudWatch, but it doesn’t provide detailed insights into the specific DDL statement causing issues. The issue is more related to the replication task logs than CloudWatch.
The TARGET_LOAD action is for controlling data loading operations, not for identifying the cause of DDL-related replication issues. This won’t capture the necessary DDL activity.
Turning on DDL activity tracing in the RDS for Oracle DB instance parameter group is not relevant to AWS DMS. DMS manages the replication process, and this parameter would not help in identifying DDL-related errors in the DMS task.
Setting the TARGET_APPLY action with LOGGER_SEVERITY_DETAILED_DEBUG level helps capture detailed logs about DDL and DML activity in AWS DMS tasks, making it the most efficient method to identify which DDL statement caused the issue.
It seems to me that the answer is:
Turn on logging for the AWS DMS task by setting the TARGET_APPLY action with the level of severity’ set to LOGGER_SEVERITY_DETAILED_DEBUG