Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Delivered
Workspace Db2
Components Monitoring
Created by Guest
Created on Nov 10, 2017

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.