Qlik Replicate: Oracle source endpoint Null values in Change Table

[Alan_Wang]

There are instances where you may find Qlik Replicate trying to insert NULL values into non-nullable or nullable columns on an update for the Change Tables using Oracle as a source. This results in the task erroring out with the following errors or NULL values that do not match the source values.

Failed (retcode -1) to execute statement: 'INSERT INTO "Schema"."TableName__CT"

Message: NULL result in a non-nullable column

The result of this occurrence is caused by Oracle as a source limitation where LOB columns can not be logged by supplemental logging so values that do not change during an update will be logged as NULL values. There is no way around this limitation. You can however change the column type to be nullable so the task would not error out.

Limitation

During Change Processing, columns without supplemental logging (e.g. LOB columns) that are not updated will be inserted as NULL in the Change Table.

Environment

• Qlik Replicate 
• Oracle source endpoint

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Investigation ID

00009901