topic Re: DB2 XML COLUMN Getting internal Error cannot parse in Qlik Replicate

DB2 XML COLUMN Getting internal Error cannot parse

ghassan1 — Thu, 30 Apr 2026 15:50:55 GMT

Hi,

I have created log stream based task that reads from DB2 LUW(source end point) and loads in DB2 LUW(ODBC target end point). Type of 1 column in source is XML, in Transform column type appears CLOB . Running task in full load, and getting error could not parse XML , invalid EOF internal error.

Taks structure:
task 1: source DB2 -> logstream

task 2: DB2 source (with logstream of task 1) -> odbc(target DB2)

getting error in task 2

If anyone faced similar error please do guide how to handle XML column in Qlik Replicate.

Thanks

Re: DB2 XML COLUMN Getting internal Error cannot parse

john_wang — Fri, 01 May 2026 00:55:41 GMT

Hello @ghassan1 ,

We need some additional information to better understand the issue:

Does the error occur during the Full Load phase, the Change Processing phase, or both?
What is the exact error message?
Can you test a direct flow from the IBM DB2 source to a DB2 ODBC target (without using LogStream)?
Are you able to confirm that the data contains valid XML?
- The XML may be corrupted due to truncation or invalid characters etc.
What's the subtype you selected?

Note: Support for a native DB2 LUW target endpoint in Qlik Replicate is planned for version 2026.5, which is expected to be released within the next few weeks.

Hope this helps.

John.

Re: DB2 XML COLUMN Getting internal Error cannot parse

ghassan1 — Sun, 03 May 2026 08:30:07 GMT

Hi john_wang,

Thanks for providing your response on this, please find below my inline response on asked questions

Does the error occur during the Full Load phase, the Change Processing phase, or both? [ error occurring in both ]
What is the exact error message? [Internal error occurred in XML parser. parser error is Gen_UnexpectedEOF. SQLSTATE= 2200M [1022502] ar odbc_stmt.c 2846]
Can you test a direct flow from the IBM DB2source to a DB2 ODBC target (without using LogStream)? [Tested direct and logstream both. Getting same error]
Are you able to confirm that the data contains valid XML?
- The XML may be corrupted due to truncation or invalid characters etc.[SOURCE has same datatype we are simply replicating data without any transformation, sourcr data type is also XML]
What's the subtype you selected? [it is CLOB AND SUBTYPE IS REGULAR, I trued with subtype XML BUT same issue]

regards,

Re: DB2 XML COLUMN Getting internal Error cannot parse

john_wang — Sun, 03 May 2026 14:52:01 GMT

Hello @ghassan1 ,

The behavior could not be reproduced with a simple sanity test. For example:

CREATE TABLE testxml(
 id INTEGER NOT NULL PRIMARY KEY,
 name CHAR(20),
 xxml XML
);

INSERT INTO testxml
VALUES (2, 'JohnW', '<?xml version="1.0"?> <name>JohnW</name>');

This scenario works as expected with Qlik Replicate. Full Load results:

Given this, I recommend opening a support ticket and including:

the table DDL
a small set of sample data (source and target, if possible)

This will allow for a more thorough investigation of the issue.

thanks,

John.

Re: DB2 XML COLUMN Getting internal Error cannot parse

ghassan1 — Sun, 03 May 2026 14:59:20 GMT

Hi @john_wang ,

Thanks for detailed explanation really appreciate.

I was also working on finding solution to this. Currently data type of column is XML Not Null. When I changed it to accept Nulls it worked fine and XML column data is also populate with exact values that source has. One more thing I noticed is that XML is missing last closing bracket > .

when I am changing it back to NOT NULL error occurs,

Re: DB2 XML COLUMN Getting internal Error cannot parse

john_wang — Sun, 03 May 2026 15:07:24 GMT

Hello @ghassan1 ,

Thanks for the detailed information however the behavior still cannot be reproduced in my labs:

CREATE TABLE testxml(
id INTEGER NOT NULL PRIMARY KEY,
name CHAR(20),
xxml XML NOT NULL
);

INSERT INTO testxml
VALUES (2, 'JohnW', '<?xml version="1.0"?> <name>JohnW</name>');

If you can provide the source table creation DDLs (for both source and target sides) and sample data then I'd like to investigate it deeper.

thanks,

John.

Re: DB2 XML COLUMN Getting internal Error cannot parse

ghassan1 — Sun, 03 May 2026 15:31:38 GMT

Hi @john_wang ,

please find below details:

Database: DB2 LUW 11.5

table DDL: creare table schema.table ( batid int not null, batch id int not null, xml_data XML not null) organised by row

same DDL deployed on target Database ( Same version of DB2 as source)

XML sample data:

<notif batno=“” <msg> Arabic text here </msg> <notif

please note above last ending closing tag is missing in sourcr xml data

Task settings:

Full load task:

source (db2 Luw) -> target (odbc for db2 Luw)

settings: metadata-> allow unlimited LOB COLUMNS chunk size 128 KB

COLUMN TYPE In transform

CLOB Regular

also tried

CLOB XML

Can you please share you task settings may be it could help resolve issue.

Thank you.

Re: DB2 XML COLUMN Getting internal Error cannot parse

DesmondWOO — Mon, 04 May 2026 04:45:06 GMT

Hi @ghassan1 ,

It looks like the error was triggered by the following setting:
Allow unlimited LOB COLUMNS, chunk size 128 KB.

Please switch to “Limit LOB size” and test again.

If you must continue using the unlimited LOB option, kindly raise a support ticket so we can consult with R&D.

Regards,
Desmond

Re: DB2 XML COLUMN Getting internal Error cannot parse

john_wang — Mon, 04 May 2026 13:18:41 GMT

Hello @ghassan1 , copy @DesmondWOO

I’m not sure whether this is the actual data row from the source or something else, but the XML is invalid. There are several issues:

Missing closing bracket for the opening tag
The <notif> tag is not properly closed with >.
Invalid attribute quotes
The quotes used are curly (“”), which are not valid in XML. They should be standard double quotes ("").
Incorrect closing tag
The closing tag is missing the / and should be </notif>.
Malformed tag structure
The final tag is incomplete and missing the closing >.

Hope this helps.

John.