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.

I would like an easy way to validate that a bound query is used to hint a dynamic query

Today, it is easy to validate that a bound query is used as a hint to a static query.  After all, there is a column updated in PLAN_TABLE when the package is bound that exploits the bound query.

But, it becomes difficult to know if a dynamic query actually uses the bound query as a hint and/or to know if all the dynamic queries that were using the bound query as a hint are now no longer running.

It would be nice if either there was a new column (LASTUSED) placed on the SYSIBM.SYSQUERY table that would store the date that the query was used for a hint AND/OR it would be really nice if the DSN_STATEMENT_CACHE_TABLE were extended with an additional column that indicated that the row for the query used a bound query as a hint (there would be no need for a date here, because the CACHED_TS column would indicate when the hint was used.

We are using the REOPT(ONCE) option for our NULLID.* packages (basically, the connect driver packages).  There are times that we need to hint a query to the DEFAULT access path that would be used for host variables.  When I install one of these hints, it is rather hard to detect if the hint was actually used or if I just got lucky and the access path happened to be the DEFAULT access path.  Having a tracking mechanism for the use of one of these hints would help us to know that we did the right thing.

Also, sometimes the application changes a query that was once hinted.  We would really like to know when one of these hints is no longer used. 

  • Larry Kirkpatrick
  • Feb 24 2020
  • Needs review
Why is it useful?
Who would benefit from this IDEA? DBAs and developers that work with tuning queries.
How should it work?

One (or both) of the tables mentioned above should be changed.  And the new column should be populated with appropriate values by Db2.

Idea Priority High
Priority Justification This has been a struggle for us.
Customer Name Mutual of Omaha
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