My Oracle Support Banner

OBIEE11g: Error "ORA-24920:column size too large for client at OCI call OCIStmtFetch" after extended varchar2 to 32767 byte (Doc ID 2145068.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Business Intelligence Server Enterprise Edition - Version 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.

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.

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.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.