Tag: Upgrade OBIEE 10g to OBIEE 11g

Data type related error in OBIEE 11g – Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P

If you receive an error like this in OBIEE 11g, this post may help you resolve the problem.  This is an error that you may get after upgrading from OBIEE 10g to 11g.

Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 59140] The evaluation of the index 11 expression on row count -1 failed. [nQSError: 59001] Binary Logical operation is not permitted on VARBINARY, INTEGER operand(s). (HY000)

DataTypeError

OBIEE 10g is a lot more forgiving than 11g.  So what worked in 10g may not work in 11g – such as data type mismatches.  For this error, you need to check the data types of your columns and the data types of the values being used in your column calculations.

For example, you may have a column formula like this …

sum(case when “Table”.”Column”=3 then 1 else 0 end)

Note the column is being used like an INTEGER. This worked in 10g, but does not in 11g.

When you check the data type in your RPD, it may show that the column is a VARCHAR.  You then will need to put quotes around the value (the ‘3’) … like this …

sum(case when “Table”.”Column”=’3’ then 1 else 0 end)

This should hopefully solve the problem.