Qlik Replicate performing full table scan on Oracle source table PK defined as REAL/FLOAT

[Steve_Nguyen]

Why does Qlik Replicate perform a full table scan on an Oracle source table PK defined as REAL/FLOAT?

Resolution

Avoid using REAL/FLOAT data types for table PKs with LOBs in the tables. 

Cause

Using an Oracle source, if the table PK in the source Oracle is defined as REAL/FLOAT and the table has LOBs, each lookup will become a full table scan due to host variable binding data type.

Environment

• Qlik Replicate