Invalid input for table issue

[QuiosaEvaristo]

Good day for all

I have created some tasks last week, included the tables  and they was running very but this week the tasks have stopped and when go to the log it shows the message bellow. All the log are showing the same issue.

Need a help hand to fix it

Tuesday, June 2, 2026

9:37 AM

00539829: 2026-06-02T09:31:34 [TARGET_LOAD     ]E:  Invalid input for table 'Table Name' in line number 1 [1022505]  (sqlserver_endpoint_imp.c:2965)

00539829: 2026-06-02T09:31:34 [TARGET_LOAD     ]E:  execute statement failed [1022505]  (sqlserver_endpoint_imp.c:3119)

00539829: 2026-06-02T09:31:34 [TARGET_LOAD     ]E:  Error executing data handler [1022505]  (streamcomponent.c:2034)

00539829: 2026-06-02T09:31:34 [TASK_MANAGER    ]E:  Stream component failed at subtask 2, component st_2_PRD-AO-T24-LSS-RES  [1022505]  (subtask.c:1504)

00539829: 2026-06-02T09:31:34 [TARGET_LOAD     ]E:  Stream component 'st_2_PRD-AO-T24-LSS-RES' terminated [1022505]  (subtask.c:1675)

00539821: 2026-06-02T09:31:34 [TASK_MANAGER ]W: Task 'PRD_AO_T24_LSS_RES_XML_LE_8kb' encountered a fatal error (repository.c:6488)

[john_wang]

Hello @QuiosaEvaristo ,

At this point, it is difficult to determine the root cause, as we do not yet know the source and target endpoint database types.

Based on our experience, it appears that you may be using a SQL Server target endpoint. If this is correct, we suggest enabling the SOURCE_UNLOAD and TARGET_LOAD components at the Verbose logging level, reproducing the issue, and then reviewing the task log files for further root cause analysis.

If you need additional assistance, I would recommend opening a support ticket and attaching the task Diagnostics Package collected with the above logging options enabled. Our support team will be more than happy to assist you further.

thanks,

John.

[QuiosaEvaristo]

hello John,

Thanks for your prompt reply

Source data base is Oracle and target is Sql Server