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.

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!)

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

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.