Spaces from Source DB2 iSeries Not Transferred When Converting to NVARCHAR2 in Oracle Target

[EY_C]

Hi Support,

We are encountering an issue during data replication from a source DB2 iSeries system to an Oracle target using Qlik Replicate.

In our environment:

• Source: DB2 iSeries

• Target: Oracle

• Transformation: Source string columns (likely CHAR type) are mapped to NVARCHAR2 on the Oracle side (thus implicitly converted from string to wstring in Replicate).

The issue is that spaces (especially trailing spaces) from the source data are not being replicated to the Oracle target. For example, a value like ' ABC ' in the source appears as ' ABC' in Oracle, with spaces stripped.

This behavior causes data mismatch and breaks downstream logic that relies on fixed-length padded strings.

Could you please confirm:

1. Is there a default behavior in Qlik Replicate that trims spaces (leading or trailing) when converting from string to wstring?

2. If so, is there a setting to preserve all spaces (especially trailing ones)?

3. Would changing the column mapping or any transformation rule help resolve this issue?

Looking forward to your guidance.

[Dana_Baldwin · Accepted solution]

Hi @EY_C 

Please add this internal parameter on the source endpoint, advanced tab:

keepCharTrailingSpaces

It is case sensitive. If you enter an exclamation point (!)in the search parameter field you can scroll down and select it, enable the checkbox, and click OK to save your edits and close the screen. Click Save on the endpoint. Tasks using this endpoint will need to be stopped and resumed before the change takes effect (endpoint properties & task settings are read during task start up).

If this is not the solution, please provide the full version of DB2 i and Qlik Replicate.

Thanks,

Dana

[EY_C]

Hello @Dana_Baldwin 

We applied the same configuration at another client by adding the internal parameter keepCharTrailingSpaces (case sensitive) under the Source Endpoint > Advanced tab, following the proper steps:

1. Entered ! in the search field, located keepCharTrailingSpaces;

2. Checked the box to enable it;

3. Clicked OK and saved the endpoint;

4. Stopped and resumed all tasks using this endpoint.

However, this time it did not take effect at the new client.

Here are the current environment details:

• DB2 i version: 7.5

• Qlik Replicate version: May 2024

Could you please help verify whether this parameter is still supported in our environment, or if any additional configurations are required?

Thank you.

[john_wang]

Hello @EY_C ,

The internal parameter keepCharTrailingSpaces for DB2 for i was introduced in Qlik Replicate 2021.11 SP3 and is supported in Replicate 2024.5. Please note that for this parameter to be effective when replicating to an Oracle target, the column data type must be CHAR, not VARCHAR. This is because Oracle automatically trims trailing spaces from VARCHAR values—a behavior that is common across most relational databases.

Regards,

John.