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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Components Security Monitoring
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.

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 3 years ago in Db2 / Security / Monitoring 3 Not under consideration