ASA Database Administration Guide
The Database Server
The database server
Recovery options
Force the database server to start after the transaction log has been lost.
{ dbsrv9 | dbeng9 } -f ...
All operating systems and servers.
If there is no transaction log, the database server carries out a checkpoint recovery of the database and then terminates—it does not continue to run. You can then restart the database server without the -f option for normal operation.
If there is a transaction log in the same directory as the database, the database server carries out a checkpoint recovery, and a recovery using the transaction log, and then terminates—it does not continue to run. You can then restart the database server without the -f option for normal operation.
During recovery, you should use the same server that you use in production. For example, if you use the network database server (dbsrv9.exe) during production, then you should use the network server for recovery because you may encounter problems as a result of the personal server's 10 connection limit. Specifying a cache size when starting the server can reduce recovery time.
For more information see Backup and Data Recovery.
dbeng9 "c:\Program Files\Sybase\SQL Anywhere 9\asademo.db" -f