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
Created by Guest
Created on Dec 4, 2019

Allow DROP db in QUIESCE mode

In a shared instance,  (multiple DBs serving different applications) its almost impossible to DROP a database,  without having to shutdown the entire Instance. 


In order to drop the database, it must be deactivated, otherwise it fails.  

So,  if you have a single db in a instance,  that's  quite easy.   Stop force  and you are done.  


but,  in a shared Instance,  with multiple production DBs  running under same instance, serving different applications,  this is quite of a challenge. 


DBA has no control on application servers, and application teams are not so collaborative some times. (they can't stop the entire application ) . 

So,  you force out the connections,  but they immediately connect again.   


So,  you have the "brillant" Idea..  let me QUIESCE the database..   This works initially,  all connections are forced off,  and you can Deactivate the database.  

All seems good. 


but,  when you try to drop it!  :-(   


You receive an error, that DB cant be dropped in while quiesced mode  !? 


So,  you are forced to UNQUIESCE it,  which allows the application to connect and implicitly activate the database again.  and you are stuck . 


Only possible solution would be to stop the entire instance or quiesce the instance,  but this will impact connections to other databases,  which can't happen in a production environment. 


Please,  add a DROP FORCE option,  or allows the DROP to happen, while the db is in QUIESCED mode.