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:
Clients:
  • 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. http://ibm.biz/IBM-Data-and-AI-Portal-Register
Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas
  • 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
  • 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.

Include failure / warning counts in mon_get_pkg_cache_stmt

It's currently not possible to monitor the failure rate of an SQL statement. For example, count of dupkey on INSERT. Likewise for 'soft' errors (warnings) like +100 - row not found on INSERT or DELETE. High rates of these can be a significant drain on system resources and typically indicate either an application problem, or a lack of understanding of the data set. The dupkey problem is particularly challenging since the system will continue to run, but unless the application captures and handles the error, it often goes unnoticed, except for issues such as excessive lock wait and contention, especially in high concurrency environments such as on pureScale.

What is proposed are two new columns in MON_GET_PKG_CACHE_STMT
1) NUM_EXEC_WITH_FAILURE - on the same scale as NUM_EXECUTIONS but only counting executions which returned a negative SQLCODE
2) NUM_EXEC_WITH_WARNING - likewise, but for positive SQLCODEs.

Additionally, LAST_ERROR_SQLCODE and LAST_WARNING_SQLCODE would help on drill-down.

There is precedent for these, since MON_GET_CONNECTION currently reports on the number of failed activities (ACT_ABORTED_TOTAL) but this is a the connection level, and isn't helpful for diagnosing failures at the statement level.
  • Guest
  • Jan 3 2019
  • Shipped
Why is it useful?
Who would benefit from this IDEA?
How should it work?
Idea Priority Medium
Priority Justification
Customer Name Steve Rees Consulting Inc
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