Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Not under consideration
Workspace Informix
Created by Guest
Created on Jun 22, 2023

JDBC suport of collection data types in scroll cursors

Currently the usage of collection data type columns in scroll cursors are disabled by default throwing an Exception with this stack trace.

Stack trace returned is:

at com.informix.util.IfxErrMsg.buildExceptionWithMessage(

at com.informix.util.IfxErrMsg.buildIsamException(

at com.informix.jdbc.IfxSqli.addException(

at com.informix.jdbc.IfxSqli.receiveError(

at com.informix.jdbc.IfxSqli.dispatchMsg(

at com.informix.jdbc.IfxSqli.receiveMessage(

at com.informix.jdbc.IfxSqli.sendStatementQuery(

at com.informix.jdbc.IfxSqli.executeStatementQuery(

at com.informix.jdbc.IfxResultSet.executeQuery(

at com.informix.jdbc.IfxStatement.executeQueryImpl(

at com.informix.jdbc.IfxStatement.executeQuery(

This behavour is a protection because if column data size > 4K the column is really stored as an smartblob, as explained in internal case:


The reasoning behind this is that collection types can grow to the size of blobs and blobs have never been supported with Informix JDBC and scrollable cursors.

The reason behind this is understandable as a smartblob cannot be part of an scroll cursor, but in most business cases, the content of the SET or LIST types in the tables are discrete values and always have a size < 4K.

This RFE is for revisiting this case and removing the protection to disable collection types in scroll cursor at the prepare phase, and fail only at runtime if the cursor retrieves a row with a column (collection data type) that is internaly a smartblob.

Said more directly, allow collection data types in jdbc scroll cursors and fail with a runtime error only if you get any row with columns internaly represented by a smartblob.

Needed By Quarter