db_drop 
With this command you delete the current database. All DBM server connections to the specified database are closed, except the one you use to execute this command.
As per the system default, the command for deleting the database is only successful if the commands that are still being executed within the database, are ended within 2 minutes. If these commands take longer, the system does not close the DBM server connections to the database, and the command for deleting the database fails.
New commands are still accepted at this time, but are no longer executed.
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 been terminated, the system stops the DBM server/s immediately.
You can enter an option in the command to specify that the database files should be retained in the Database Manager program after the database has been deleted.
Prerequisites
The database is in the OFFLINE operational state.
You have the server permission InstallMgm.
The Scheduler is inactive (see: scheduler_stop).
Structure
db_drop [-f] [WITHOUTFILES]
Option |
Description |
|---|---|
-f |
If you specify this option, all DBM server connections to the database are closed immediately, even if DBM commands are still being executed using the connections. 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 -f option and DBM commands are still being executed in the database, the command db_drop fails. |
WITHOUTFILES |
If you specify this option, the database service is deleted, but the database files (volumes, log files, and so on) remain in the file system. You can only access these files using operating system tools; you can no longer access them using database tools. If you do not specify this option, all the database files will also be deleted. |