Желательно указать, что за операционка и какая версия ASE

Вот нашел такие рекомендации для ASE 12.5.2 , тебе может не подойти, хотя ситуация похожая -

User database gets timeslice error at boot up. Stack includes: ds__recoverdbs, dorecover, boot__recover_and_online, rec_analyze_log, and analyze_rec_ckpt

1. Set status to bypass recovery (-32768)

2. Reboot ASE.

3. dbcc dbrepair(db_name, ltmignore)

4. Suicide log. ( Что такое - не понял )

5. Reset status of user db.

6. Reboot ASE. Then run dbcc checks on user db.

Вот что такое Suiciding log

Suiciding the log refers to a process that tells the server to ignore
the contents of the log during recovery. This is very dangerous, the
log is the guarantee of transactional consistency, if you suicide the
log
the data in the database will likely no longer be consistent (committed
modifications may not be reflected in the database, uncommitted
modification may
end up being applied, etc., and you may even introduce corruption in the
system tables.

It is sometimes used as a last resort in cases where serious errors
are encountered during recovery, to gain access to what data there is,
regardless of it's transactional consistency, in cases where there is
no better solution (i.e. it is found that the DBA hasn't taken a backup
in three years)

1.. update sysdatabases set status=-32768, status2=0 where
name='suspect_database'
2.. shutdown with nowait
3.. restart dataserver
4.. dump tran suspect_database with no_log
5.. update sysdatabases set status=12, status2=0 where
name='suspect_database'
6.. recycle dataserver