3420949 - Corrupt databases and it's affect on database recovery order and enable logins during recovery - SAP ASE

• • There is a database (auditdb) that needs to be recovered first AND needs to be online before all other databases. 
  • The other databases will have audit triggers that will write to the auditdb and if that first database is not online, the triggers will fail writing to the audit table and data will be lost. 
  • To force recovery of this database, two configurations are enabled:  
    sp_configure 'enable logins during recovery', 0 -- turn off all logins until the server is fully recovered.
    go
    sp_dbrecovery_order auditdb, 1, null, strict
    go
    --OR -- 
    sp_dbrecovery_order auditdb,1, force, strict
    go
     
  • This leads to a few questions:  
    1. What happens if the auditdb is corrupted, or is not recovered?
    2. Will an unrecovered database keep all accounts from logging in until it is fully recovered? 
    3. Would like to keep all users out until the server is fully recovered.
    4. If a specific database doesn't recover:
       • Does it prevent the other databases from recovering until it's been recovered?
       • Or will it allow the other databases to recover?
       • Since logins are locked, during recovery, users will not be able to log into the system until, the specific database has recovered, or all databases have recovered?
    5. What is the difference between "null, strict", and "force, strict"?
    6. If the server needs to be opened to all users, without the specific database being recovered, how is the done?
    7. Any other issues not covered in this list?

SAP Adaptive Server Enterprise (ASE) all versions

KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To