db_drop 
You delete the current database instance. All DBM server connections to the specified database instance have to be closed, apart from the ones you use to execute this DBM command.
The system default value is that the command for deleting the database instance is only successful if the commands that are still being executed are ended within 2 minutes. New commands are still accepted at this time, but are no longer executed. If this DBM command takes longer to execute, the system does not close the DBM server connections to the database instance, and the command for deleting the database instance fails.
You can enter an option in the command to force the system to close the DBM server connection/s. Instead of waiting until current DBM commands have finished, the system stops the DBM server/s immediately.
You can use an additional option to specify that the database files be retained in the Database Manager after they have been deleted from the database instance.
Prerequisites
The database instance is in the OFFLINE operational state.
You have the server authorization InstallMgm.
the Scheduler is deactivated (see: scheduler_stop).
Structure
db_drop [-f] [WITHOUTFILES]
Option |
Description |
|---|---|
-f |
If you specify this option, all connections of the DBM server to the database instance are terminated immediately and the database instance is deleted, even if this connection was being used for executing DBM commands on the database instance at the same time. The command line windows in question then no longer function. As soon as you enter another DBM command, an error message is displayed. If you do not specify the option -f and DBM commands are still being executed in the database instance, the command db_drop fails. |
WITHOUTFILES |
The database files are not deleted. If you do not specify this option, all the database files will also be deleted. |
More Information
Database Manager CLI Tutorial, Deleting a Database Instance