Database Shutdown

There are a few occasions when a database needs to be shut down. For example, when a new foreign key needs to be inserted the database should be shut down in order to avoid the annoying message Object in use. A registered database can be shut down simply and quickly using the IBExpert Services menu item Database Shutdown.

Select the registered database which is to be shut down. Then select one of the following options, to specify how active transactions should be dealt with:

• Forced: In this mode all transactions, that are still active at the stated time, are aborted regardless of their type or importance, and all users are forcefully disconnected. As Firebird/InterBase® transactions function stably and securely, there are very few areas of application where this forced mode should not be used.
• Deny new transactions: In this mode all transactions must be executed by the stated time. Any new transactions that are started are blocked. If there are any transactions that are still active by the stated time, the database shutdown is not executed.
• Deny new attachments: With this option all active user attachments must finish their work by the stated time. If some attachments are still active by the stated time, the database shutdown is not executed.
• Wait: The period of time (in seconds) until the shutdown is executed can be specified here.

The online/shutdown modes are available for Firebird 2.5 and above.

Then simply click Shutdown to shutdown the database. To bring the database back online, choose the IBExpert Services menu item Database Online.

Firebird 2.0 introduced new -shutdown parameters to be used with gfix. Please refer to the Firebird 2.0.4 Release Notes chapter, Command-line utilities for further information.

Firebird 2.5 exposes a variety of API functions for instigating server shutdowns of various types from client applications. Please refer to the Firebird 2.5 Release Notes chapter, Shutdown functions for further information.