How does Oracle Business Intelligence Handle CLOB Data Type? (Doc ID 580436.1)

Last updated on JULY 18, 2017

Applies to:

Business Intelligence Suite Enterprise Edition - Version 10.1.3.4.1 [1900] and later
Business Intelligence Server Enterprise Edition - Version 10.1.3.4.1 [1900] to 11.1.1.6.2 [Release 10g to 11g]
Information in this document applies to any platform.
***Checked for relevance on 25-Oct-2013 ***

Goal

 

When you try to use CLOB datatype in Analytics it might fail with the following error:                            


Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 16001] ODBC error state: S1000 code: 932 message: [Oracle][ODBC][Ora]ORA-00932: inconsistent datatypes: expected - got CLOB. [nQSError: 16001] ODBC error state: S1000 code: 932 message: [Oracle][ODBC][Ora]ORA-00932: inconsistent datatypes: expected - got CLOB. [nQSError: 16015] SQL statement execution failed. (HY000)

SQL Issued: SELECT "SLX Tickets"."Ticket ID" saw_0, "SLX Tickets".Area saw_1, "SLX Tickets"."Problem Resolution" saw_2, "SLX Urgency Codes"."Urgency Description" saw_3, "SLX Completed By"."Completed By Name" saw_4, "SLX Assigned Date"."SLX Assigned Date - Year Number" saw_5 FROM "Sales Logix Data Warehouse" WHERE "SLX Assigned Date"."SLX Assigned Date - Year Number" = 2008 ORDER BY saw_0, saw_1, saw_

 

 

 

Solution

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