ASA Database Administration Guide
Database Administration Utilities
With the Erase utility, you can erase a database file or write file and its associated transaction log, or you can erase a transaction log file or transaction log mirror file. All database files, write files, and transaction log files are marked read-only to prevent accidental damage to the database and accidental deletion of the database files.
Deleting a database file that references other dbspaces does not automatically delete the dbspace files. If you want to delete the dbspace files on your own, change the files from read-only to writable, and then delete the files individually. As an alternative, you can use the DROP DATABASE statement to erase a database and its associated dbspace files.
If you erase a database file or write file, the associated transaction log and transaction log mirror are also deleted. If you erase a transaction log for a database that also maintains a transaction log mirror, the mirror is not deleted.
The database to be erased must not be running when this utility is used.
Exit codes are 0 (success) or non-zero (failure).
You can access the Erase utility in the following ways:
From Sybase Central, using the Erase Database wizard.
At the command prompt, using the dberase command. This is useful for incorporating into batch or command files.
For more information, see the DROP DATABASE statement.
Erasing a database using the Erase Database wizard
Erasing a database using the dberase command-line utility