OBIEE11g: Error "ORA-24920:column size too large for client at OCI call OCIStmtFetch" after extended varchar2 to 32767 byte
Last updated on JULY 03, 2016
Applies to:Business Intelligence Server Enterprise Edition - Version 220.127.116.11.150120 and later
Information in this document applies to any platform.
Oracle Database 12c has a new feature MAX_STRING_SIZE that could increase the maximum size of VARCHAR2 and that of NVARCHAR2 Database column to 32767 bytes.
- About MAX_STRING_SIZE in Oracle Database 12c, please refer oracle database document. MAX_STRING_SIZE
OBIEE 11g connects to Oracle Database 12c as a datasource; the following error returned when fetching the column whose size has been extended to 32767 bytes against Oracle Database 12c.
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: 17001] Oracle Error code: 24920, message: ORA-24920: column size too large for client at OCI call OCIStmtFetch. [nQSError: 17012] Bulk fetch failed. (HY000) SQL Issued: SELECT 0 s_0, "SYSTEM"."TEST_TABLE"."EXTENDED_VARCHAR" s_1, "SYSTEM"."TEST_TABLE2"."E2" s_2 FROM "SYSTEM" FETCH FIRST 65001 ROWS ONLY
1. Extended max_string_size to 32767 bytes on Oracle Database 12c.
2. Change the column length more than 4000 bytes in the physical layer in OBIEE 11g repository.
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