Show TOC

admin quiesce_checkLocate this document in the navigation structure

Determines if the queues in the Replication Server have been quiesced.

admin quiesce_check
Example 1

The TOKYO_RS Replication Server is quiescent.

admin quiesce_check
Replication Server TOKYO_RS is quiesced
Example 2

This message indicates that the system is not quiescent because there are unread messages in queue 103:1. The reported Read location (30.2) and Write location (32.1) show that more blocks in the queue have been written than read. Assuming no more blocks are written, the Read location must advance to segment 32, block 2, before the system becomes quiescent.

admin quiesce_check
Can’t Quiesce. Queue 103:1 has not been read out.
 Write=32.1 Read=30.2
  • admin quiesce_check determines if a Replication Server is quiescent.

  • The Replication Server is quiescent if:
    • There are no subscription materialization queues.

    • Replication Server has read and processed all messages in all queues.

    • No inbound (RepAgent) queues contain undelivered committed transactions.

    • All messages in RSI queues have been sent to their destination Replication Servers and acknowledgments have been received.

    • All messages in DSI queues have been applied and acknowledgments received from data servers.


Any user may execute this command.