“in quiesce” database log record value updated

If you start the secondary server using the -q option of dataserver, for each user database marked internally as “in quiesce,” Adaptive Server issues a message at start-up stating that the database is "in quiesce."

-q recovery for databases copied with quiesce database for external dump acts much like the recovery for load database. Like recovery for load database, it internally records the address of the current last log record, so that a subsequent load transaction can compare this address to the address of the previous current last log record. If these two values do not match, then there has been original activity in the secondary database, and Adaptive Server raises error number 4306.