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,
Post an idea
Upvote ideas that matter most to you
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.
More efficient unique indexes for monotonically increasing keys and constraints
Currently an index on a SERIAL and other monotonically increasing keys only add to the last node in the index causing the node to split into two half filled nodes. Eventually a sufficient number of nodes have so split that the index's search effic...
SELinux policies for Informix on RHEL version 7 and upwards
At startup the Informix database spawns a number of processes, that run as unconfined SeLinux processes. From the permission perspective, some of these processes run as informix user (example: cpu and encrypt vps) whilst others run as root user (l...
For RSS and HDR nodes partition the apply work by transaction id instead of partnum.
For RSS and HDR nodes currently the apply work is partitioned across threads by partnum,
We would like the option to partition the work across apply threads by transaction id.
Currently RSS apply threads have to syncronise with the other apply...
Different message when transaction time limit reached
When transaction duration limit is reached the following message occurs in the online log file 08:56:28 sid 11617 - email@example.com - pid 6811 terminated because session transaction duration (60 seconds) has exceeded limit. This session i...
Enhancement to DROP PROCEDURE / DROP FUNCTION syntax
Currently, the DROP PROCEDURE statement requires that the all of the procedure parameters necessary to completely identify the specific procedure. This is important due to Informix supporting polymorphic procedures, and is generally a good thing. ...
On restore or chunk addition allow automatic creation of files in certain folders.
On restore or chunk creation allow automatic creation of cooked files. Add an onconfig parameter which contains a list of folders where automatic cooked chunk creation is allowed. Cooked chunk files can be automatically created in this folder of a...
SQLTrace offers the DBA the tooling required to monitor a user session. However its difficult to monitor heavily used systems. For example one needs to have a buffer large enough to store 90 seconds of SQL queries (small lookup SQL's consume the b...
We need to stay with Informix 12 so that our compiled 4GL will continue to work, but we would like to upgrade to RHEL8. Others have done this and it works for them, but my company has to get confirmation that this will be a supported combination f...
Limit open partitions to avoid very large rsam pool
In systems with a lot of tables informix can have a very large rsam pool. This can cause informix to allocate so much memory it starts swapping or in memory limiting versions (like workgroup, express etc.) to even let the engine crash. Sometimes t...
Do not place IBM confidential, company confidential, or personal information into any field.