well .. if you are using Sybase I can answer for you..
1. set allow updates to sys tables on
2. update the sysdatabses.status for the dbid in question to -32768
3. shutdown server & backup server
4. restart server and backup server
-- you are now in no recovery mode for the db with status set to -32768
5. load the database in question from a dump ..
6. set sysdatabases.status for that dbid to zero
7. shut off allow updates to sys tables
you may have to change status2 from (say 77=offline) to zero ..
-- or online database <dbname>
that is if you have a backup
if not skip the load, and drop the database ..
- drop database <dbname>
This is actually a bug in Sybase. A DBMS should never go into log suspend during recovery. Sybase introduced LCR, a log compensation mechanism in ASE 11.9.2 onwards, but the solution was an half cooked implementation.
If you are in log suspend, simply alter the database in bypass recovery mode.
change master..sysdatabases(status) column to -32768
change the status to the 0
shutdown with nowait, important to shutdown with nowait when any db's are in by-pass recovery otherwise you will inadvertently suicide the log.