IBM Data & AI

 Welcome to the IBM Data & AI Ideas Portal for Clients! 

We welcome and appreciate your feedback on IBM Data & AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.  If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.
  • If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity.
Additional Information:
  • The shorter URL for this site is:
  • To view our roadmaps:
  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Flag high volatile tables as 'VOLATILE' and access those tables differently than normal tables by the query optimizer

A volatile table is defined as a table whose contents can vary from empty to very large at run time. In other words , statistics data is often out of date and may result in wrong access plans by the optimizer and subsequently may have lock the entire table than the particular row in certain cases even we implemented  row level locking on such tables.

  • Guest
  • Feb 7 2020
  • Needs review
Why is it useful?
Who would benefit from this IDEA? All of the customers with such access pattern and finally the whole informix DB server use community
How should it work?

The proposed solution would be to use better query access plans by the optimizer and avoid such unforeseen table access locking issues. This issue is a common issue in most of our bigger customer sites with high transactional work activity when accessing highly volatile table data. Current workaround would be: , To add dummy records and keep as it is (without getting empty during transactions) to trat this as a normal table or run update statistics when we have a considerable number of records and keep this inconsistent statistics without clearing on such tables. However, this would be a painful process as we need to consideror treat each individual tables seperately.  If we have proper solution, It is clear we would get most of the benifits to support and run customer's business operations to run smoothly without our interference.


Idea Priority High
Priority Justification As there are more than 1000 of customer sites, it would be hard and time consuming process to treat such volatile table in a manual way.
Customer Name Pronto Software Ltd
Submitting Organization
Submitter Tags
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions