"ORA-00932: inconsistent datatypes: expected - got CLOB" Is Signalled In ODI Mapping With Lookup Set To "Select last single row"

(Doc ID 2185230.1)

Last updated on OCTOBER 04, 2016

Applies to:

Oracle Data Integrator - Version to [Release 12c]
Information in this document applies to any platform.


Executing an Oracle Data Integrator (ODI) Mapping with CLOB attributes and Lookup components throws the error if the Lookup "Match Row Rules" > "Multiple Match Rows" is set to "Select last single row" in the Logical view:


ODI-1228: Task Load D_MD_VOUCHER_COMMENTS-IKM Oracle Merge- fails on the target connection DWMIG.
Caused By: java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:407)
  at ...


The same Mapping does successfully execute if the Lookup "Match Row Rules" > "Multiple Match Rows" is set to "All rows (number of result rows may differ from the number of input rows)".



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms