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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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

Status Not under consideration
Workspace Db2
Components Monitoring Security
Created by Guest
Created on Feb 11, 2015

implicit GRANT EXECUTE to SYSMON authority for all monitor routines(RIMS)

Customer has to grant the EXECUTE privilege on the monitoring functions to a user who already has the SYSMON authority. They would expect that a user of the SYSMON_GROUP holds this privilege implicitly. This looks like a restriction to the monitoring users. The main issue here is that SYSMON is an instance level authority and that the routines are considered for database level authority. SYSMON authority will only apply to the 'legacy monitoring infrastructure' which is SNAPSHOT based because the snapshot API makes use of an INSTANCE ATTACH rather than a database connection. This is why SYSMON is an Instance level authority rather than a database authority. The monitor routines makes no use of the snapshot infrastructure and relies on database connections. SQLADM is a database level authority rather than an instance authority. The current design of the monitoring routine infrastructure is therefore not sensitive to SYSMON authority. As the customer understood the 'legacy snapshot infrastructure' is not 'the future'. But he doesn't understand the benefit of a SYSMON group when it's necessary to grant explicit SQLADM rights only for monitoring in every database of a company. If a user is member of the SYSMON group he wants to monitor everything. If the customer wants to implement a monitoring software he must now grant SQLADM to a monitoring userid in maybe hundreds of databases! Also there is a 'risk' with SQLADM: If someone has SQLADM he is allowed to start an offline reorg with ALLOW NO ACCESS against a production system which can mean that this system stands still maybe for hours. So please implicitly GRANT EXECUTE to SYSMON authority for all monitor routines.
  • Guest
    Jul 1, 2019

    Idea returned as a duplicate of this idea.


Introduce MON_ADM privilege for monitoring purposes

A MON_ADM privilege will be useful for monitoring tasks, manually or automatically like through Data Server Manager or IBM ITM. Such a privilege will only enable the user to use the monitoring framework table functions and adjacent functionality r...
over 5 years ago in Db2 / Monitoring / Security 3 Not under consideration