Qlik Replicate: ORA-00932 inconsistent datatypes: expected NCLOB got CHAR

Alan_Wang — Tue, 03 Feb 2026 09:17:14 GMT

PostgreSQL Source tables with a Character Varying (8000) datatype would be created as a Varchar(255) datatype on the Oracle Target tables as the default.

This error will occur with the default settings, as Oracle only supports up to 255 characters for the datatype. Incoming records with a character count higher than 255 are treated as a CLOB datatype and cannot fit in all of the incoming 8000 bytes/char of data.

The following error is written to the log:

[TARGET_APPLY ]T: ORA-00932: inconsistent datatypes: expected NCLOB got CHAR [1020436] (oracle_endpoint_bulk.c:812)

Environment

Qlik Replicate any version
PostgreSQL Source
Oracle Target

Resolution

Adjust the datatype in the Qlik Replicate task table settings to transform the character varying (8000) datatypes to a CLOB datatype.

This will create CLOB columns on the target and allow the large incoming records to fit in the target table.

Note that the transformation will need a target table reload to rebuild the table with a new datatype.

Cause

Default task settings create the column with a varchar(255) datatype, while it needs to be a CLOB datatype, as any size over 255 will not fit in the target table if an incoming record exceeds 255 characters in size.

article Qlik Replicate: ORA-00932 inconsistent datatypes: expected NCLOB got CHAR in Official Support Articles

Qlik Replicate: ORA-00932 inconsistent datatypes: expected NCLOB got CHAR

Environment

Resolution

Cause