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 Future consideration
Workspace Db2
Components Serviceability
Created by Guest
Created on Nov 4, 2024
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit DB24LUW-I-265 Allow offline backup to automatically force all Allow offline utilities such as backup, restore, rollforward to auconnections.

Restricted access at a database level quiesce to prevent database activation in order to perform exclusive access operations like offline backup/restore in a multi database instance. Merged

In a multi database system especially when running applications on platforms like OpenShift or even application servers like WAS where applications reconnect very fast, it becomes very hard or even impossible to get exclusive access to a single database.

The options at hand today are either not effective or way too restrictive.

QUIESCE INSTANCE e.g. would block access to all databases which is not desirable. Also blocking an incoming IP address from an Open Shift environment would have the same undesirable effect as QUIESCE INSTANCE.

QUIESCE DATABASE on the other hand has little, or in most cases no effect when trying to get exclusive access to the database, especially in a pureScale environment.

The reason why QUIESCE DATABASE is ineffective is due to that QUIESCE CONNECT is a database privilege and the database has to be activated, and the connection has to be established to check if the account has the privilege.

To prevent database activation to allow exclusive access e.g. for offline backup or restore, we would need something similar to the QUIESCE INSTANCE RESTRICTED ACCESS but on the database level, which like on the instance level would prevent authorization checking for all connect attempts to the database, and only allow user IDs with SYSADM, SYSCTRL or SYSMAINT to connect to the database.

Needed By Yesterday (Let's go already!)
  • Guest
    Reply
    |
    Nov 21, 2024

    I notice that you have merged my idea with another similar idea. I think my idea is more generic and would provide possibilities to do other maintenance work on a single database which might require the database to be blocked for access from applications or other users. 

    To me it would make more sense to merge the other idea to this one since this idea would solve the problem described in the other idea but also allow for other tasks that may need exclusive access to the database.

    It also makes more sense to have control over the time the database is in restricted mode without the risk that applications or user can connect in between operations.