If you are using the warm standby method to back up a quiesced database, SAP ASE must know whether it is starting the primary or the secondary server.
The databases are recovered normally, rather than as they would be for load database.
Any uncommitted transactions at the time you issue quiesce database are rolled back.
Not marked in quiesce – under the -q option, if a database is not marked in quiesce, it is recovered as it would be in the primary server. That is, if the database is not currently in a load sequence from previous operations, it is fully recovered and brought online. Any incomplete transactions are rolled back, and compensation log records are written during recovery.
User databases – user databases that are marked in quiesce recover in the same manner as databases recovering during load database. This enables load tran to detect any activity that has occurred in the primary database since the server was brought down. After you start the secondary server with the -q option, the recovery process encounters the in quiesce mark. SAP ASE issues a message stating that the database is in a load sequence and is being left offline. If you are using the warm standby method, do not bring the database online for its decision-support system role until you have loaded the first transaction dump produced by a dump tran with standby_access. Then use online database for standby_access.
System databases – system databases come fully online immediately. The in quiesce mark is erased and ignored.