By using AWS re:Post, you agree to the Terms of Use

AWS DMS - FATAL_ERROR - Stream component failed at subtask - SQL Server to Redshift

0

Hello All

I am migrating RDS for ms sql server to redshift and getting below error. When checked with 'Table Statistics', one of them is showing as 'Table error'. please advise to resolve the issue

Error :

Last failure message Last Error Fatal error has occurred Task error notification received from subtask 7, thread 0 [reptask/replicationtask.c:2883] [1022505] Error executing source loop; Stream component failed at subtask 7, component st_7_ORXNENHJMUOQANKGRR5D3EZGLL2UWEW2C5MXXZY; Stream component 'st_7_ORXNENHJMUOQANKGRR5D3EZGLL2UWEW2C5MXXZY' terminated [reptask/replicationtask.c:2891] [1022505] Stop Reason FATAL_ERROR Error Level FATAL

please find the below cloudwatch logs and advise if there is any issue

2022-07-26T13:01:15 [SOURCE_UNLOAD ]E: RetCode: SQL_ERROR SqlState: 42000 NativeError: 102 Message: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Incorrect syntax near 'FTP'. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:3932)

2022-07-26T13:01:15 [SOURCE_UNLOAD ]E: sqlserver_fill_table_partitioners_names(...) Failed to create statement: select pf.name AS PartitionFunctionName, c.name AS PartitionKey FROM sys.dm_db_partition_stats AS pstats INNER JOIN sys.partitions AS p ON pstats.partition_id = p.partition_id INNER JOIN sys.destination_data_spaces AS dds ON pstats.partition_number = dds.destination_id INNER JOIN sys.data_spaces AS ds ON dds.data_space_id = ds.data_space_id INNER JOIN sys.partition_schemes AS ps ON dds.partition_scheme_id = ps.data_space_id INNER JOIN sys.partition_functions AS pf ON ps.function_id = pf.function_id INNER JOIN sys.indexes AS i ON pstats.object_id = i.object_id AND pstats.index_id = i.index_id AND dds.partition_scheme_id = i.data_space_id AND i.type <= 1 INNER JOIN sys.index_columns AS ic ON i.index_id = ic.index_id AND i.object_id = ic.object_id AND ic.partition_ordinal > 0 INNER JOIN sys.columns AS c ON pstats.object_id = c.object_id AND ic.column_id = c.column_id WHERE pstats.object_id = OBJECT_ID(N'[dbo].['FTP Actions International$']', N'table') group by pf.name, c.name [1022505] (sqlserver_endpoint_metadata.c:1517)

2022-07-26T13:01:15 [SOURCE_UNLOAD ]E: sqlserver_construct_select_statement(...) unable to resolve partitioners names for table dbo.'FTP Actions International$' [1022505] (sqlserver_endpoint_unload.c:637)

2022-07-26T13:01:15 [SOURCE_UNLOAD ]E: SQL Server source. Cannot init table workspace for iMetaDataTableid- '27' [1022505] (sqlserver_endpoint_unload.c:415)

2022-07-26T13:01:15 [SOURCE_UNLOAD ]E: Error executing source loop [1022505] (streamcomponent.c:1873)

2022-07-26T13:01:15 [TASK_MANAGER ]E: Stream component failed at subtask 4, component st_4_QQMN67PX7YCFOKBMLC6N2VUUZYDNUVLMALF3VBY [1022505] (subtask.c:1414)

2022-07-26T13:01:15 [SOURCE_UNLOAD ]E: Stream component 'st_4_QQMN67PX7YCFOKBMLC6N2VUUZYDNUVLMALF3VBY' terminated [1022505] (subtask.c:1594)

2022-07-26T13:01:15 [TASK_MANAGER ]W: Table 'dbo'.''FTP Actions International$'' (subtask 4 thread 0) is suspended (replicationtask.c:2550)

2022-07-26T13:01:15 [TASK_MANAGER ]I: Task - 2QFN76MQVCH2LN5WWULZTGTJJSH6Q6OBTQKHLLQ is in ERROR state, updating starting status to AR_NOT_APPLICABLE (repository.c:5102)

2022-07-26T13:01:15 [TASK_MANAGER ]E: Task error notification received from subtask 4, thread 0 [1022505] (replicationtask.c:2883)

2022-07-26T13:01:15 [TASK_MANAGER ]E: Error executing source loop; Stream component failed at subtask 4, component st_4_QQMN67PX7YCFOKBMLC6N2VUUZYDNUVLMALF3VBY; Stream component 'st_4_QQMN67PX7YCFOKBMLC6N2VUUZYDNUVLMALF3VBY' terminated [1022505] (replicationtask.c:2891)

2022-07-26T13:01:15 [TASK_MANAGER ]E: Task '2QFN76MQVCH2LN5WWULZTGTJJSH6Q6OBTQKHLLQ' encountered a fatal error (repository.c:5196)

1 Answers
0

the error is not clear from the messages available. Please refer to earlier log entries in cloudwatch log for the task. It could be query failure or conversion failure which could result in fatal error. If the logs not conclusive then you might want to open a case with aws premium support who could help troubleshoot the issue

answered a month ago
  • Hi, thanks for checking. Updated cloudwatch logs, if you find any issues kindly advise

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions