IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on Mar 12, 2018

Page limitation for single fragment, to avoid stop the business and recreate the table .

Remove or enlarge the 16,775,134 page limitation per fragment.
  • Guest
    Jun 2, 2020

    This issue has been around for a long time but with trends towards Big Data and just Informix systems being around for longer, dealing with this problem comes up fairly frequently.

    There are a few aspects to it. Ideally it would be good to sweep away this limitation entirely but given it is there it presents the following challenges:

    1. Monitoring all tables and table fragments for the page limit and making predictions around when it might be reached based on table growth. I don't think there is anything in InformixHQ to do this, for example. Doing something here seems like the bare minimum to avoid a nasty surprise for the uninitated.

    2. Workgroup edition users cannot use partitioning. This is understandable from the point of view of detach/drop, PDQ, other enterprise features but should not limit table size.

    3. With a 2 kB page size, the unpartitioned table size limit is just 32 GB. Larger page sizes can help but only where the table is wide enough to use large page sizes (avoiding reaching another limit, 255 rows/page).

    4. Range partitioning offers a possible solution, provided table have a suitable interval column, but sizing of the interval must be done carefully.

    If the current constraints are not addressed it would perhaps be good to have an advisor of some kind to:

    • suggest the ideal page size for table.

    • suggest an interval column and interval size.

    • a method to easily convert a standard non-partitioned table to range partitioning.

    This should take compression into consideration too and perhaps replace the compression estimator.

    There could be an easy way to convert tables to range partitioning with minimal changes on disk or alternatively loopback replication could be used.

    If the limitation is to be addressed fully, we would not mind a new dbspace type and would not necessarily expect existing dbspaces to automatically be converted or fixed.