topic Re: Invalid input for table issue in Qlik Replicate

Invalid input for table issue

QuiosaEvaristo — Tue, 02 Jun 2026 08:40:04 GMT

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)

Re: Invalid input for table issue

john_wang — Tue, 02 Jun 2026 09:03:05 GMT

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.

Re: Invalid input for table issue

QuiosaEvaristo — Tue, 02 Jun 2026 09:55:28 GMT

hello John,

Thanks for your prompt reply

Source data base is Oracle and target is Sql Server

Re: Invalid input for table issue

QuiosaEvaristo — Thu, 04 Jun 2026 09:42:21 GMT

Hi Jonh

The tables have one column with name XMLRECORD with type XML.
I have altered the data type from XML to Varchar it works without any error. We need the data type of this column to remain with the type of XML.

---------------------------------- The error ----------------------------------------------------------------------------------

00542383: 2026-06-02T11:35:59 [TARGET_LOAD ]E: Failed (retcode -1) to execute statement: 'INSERT INTO [T24USER].[F_MD_PARAMETER]([RECID],[XMLRECORD]) values (?,?)' [1022502] (ar_odbc_stmt.c:2858)

00542383: 2026-06-02T11:35:59 [TARGET_LOAD ]E: RetCode: SQL_ERROR SqlState: 42000 NativeError: 9400 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]XML parsing: line 158, character 0, unexpected end of input Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:2864)

00542383: 2026-06-02T11:35:59 [TARGET_LOAD ]E: Invalid input for table 'T24USER'.'F_MD_PARAMETER' in line number 1 [1022505] (sqlserver_endpoint_imp.c:2965)

00542383: 2026-06-02T11:35:59 [TARGET_LOAD ]E: Execute statement failed [1020403] (sqlserver_endpoint_imp.c:4644)

00542383: 2026-06-02T11:35:59 [TARGET_LOAD ]E: Handling End of table 'T24USER'.'F_MD_PARAMETER' loading failed by subtask 3 thread 1 [1022505] (endpointshell.c:3208)

00542383: 2026-06-02T11:35:59 [TARGET_LOAD ]E: Error executing data handler [1022505] (streamcomponent.c:2034)

00542383: 2026-06-02T11:35:59 [TASK_MANAGER ]E: Stream component failed at subtask 3, component st_3_PRD-AO-T24-LSS-RES [1022505] (subtask.c:1504)

00542383: 2026-06-02T11:35:59 [TARGET_LOAD ]E: Stream component 'st_3_PRD-AO-T24-LSS-RES' terminated [1022505] (subtask.c:1675)

Re: Invalid input for table issue

SachinB — Thu, 04 Jun 2026 10:55:53 GMT

Hello @QuiosaEvaristo ,

Based on the logs provided, the failure occurs when SQL Server attempts to insert data into the target XML column. The reported error is:

"XML parsing: line 158, character 0, unexpected end of input" (SQL Server Native Error 9400)

This error is generated by SQL Server's XML parser and indicates that the XML document being inserted is not well-formed. Specifically, SQL Server detected that the XML content ended unexpectedly while parsing the document, which may be caused by incomplete XML content, missing closing tags, invalid XML formatting, or truncated data.

As part of the investigation, the target column was changed from XML to VARCHAR, and the load completed successfully. This indicates that Qlik Replicate is able to transfer the data, but SQL Server rejects the value when validating it as XML.

We would recommend. Identify the source record(s) being processed when the error occurs.

Extract and validate the XML content from the source system.
Verify that the XML document is complete, well-formed, and contains all required closing tags.
If the XML is confirmed to be valid at the source, compare the source and target payload lengths to determine whether the XML content is being truncated before reaching SQL Server.

We hope this information is helpful. If you would like us to investigate this further together, please open a support case and we will be happy to assist with the analysis.

Regards,

Sachin B

Re: Invalid input for table issue

john_wang — Thu, 04 Jun 2026 14:13:05 GMT

Hello @QuiosaEvaristo ,

Thanks for the update.

Based on the error message:

XML parsing: line 158, character 0, unexpected end of input

it appears that the XML data may be incomplete or corrupted. Please check the following:

Verify that the source data contains valid XML.
Ensure that no truncation occurs during extraction, transfer, or loading of the XML data.
Check the maximum size/length of the XML column and confirm that the entire XML document is being processed.
Verify that the XML data does not contain any invalid or unsupported characters.
Confirm the Oracle Client installation type on the Replicate server. Please note that XML data types require a full Oracle Client installation; the Oracle Instant Client is not sufficient for XMLTYPE columns.

Thanks,

John.

Re: Invalid input for table issue

QuiosaEvaristo — Thu, 04 Jun 2026 14:47:48 GMT

Hi SachinB,

Thanks for the feedback

Re: Invalid input for table issue

QuiosaEvaristo — Thu, 04 Jun 2026 14:48:15 GMT

Hi John

Thanks for the feedback