Troubleshoot Unable to get table definition for table '0' cause by a DDL command (cant find the DDL in the logs)

0

Hello

Im currently using DMS and got the following message 2022-10-30T09:40:03 [SOURCE_CAPTURE ]E: Unable to get table definition for table '0' [1021802] (oracle_endpoint_capture.c:759)

and found the following info

https://community.qlik.com/t5/Official-Support-Articles/SOURCE-CAPTURE-E-Unable-to-get-table-definition-for-table-0/ta-p/1809603 I was looking towards enabling source capture for DDL commands in SOURCE_CAPTURE

Im looking towards a way to enable trace only for ddl commands (traceDdlChanges?) to dump the exact command which failed. Activating full debug trace for SOURCE_CAPTURE is not an option at all. Too much verbose for an event that may happen very occasionally

I couldnt find any further information https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.Logging.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DDLHandling.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.ErrorHandling.html

Thanks

質問済み 1年前316ビュー
1回答
0

hello, you may extract the table DDL from both source and target side to see the difference in the DDL structure and identify the change and source of change to take care in future changes via deployments or manual code change windows.

AWS
rds_dba
回答済み 9ヶ月前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ