admin quiesce_force

Determines whether a Replication Server is quiescent and forces it to deliver and obtain acknowledgments for messages in RSI queues.

Syntax

admin quiesce_force_rsi

Example 1 – The TOKYO_RS Replication Server is quiescent.

admin quiesce_force_rsi

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 Write location (32.1) and Read location (30.2) show that more blocks in the queue have been written than read.
```
admin quiesce_force_rsi
```
```
Can’t Quiesce. Queue 103:1 has not been read out.
Write=32.1 Read=30.2
```

Execute suspend log transfer from all before you execute admin quiesce_force_rsi. This prevents RepAgents from connecting with the Replication Server.
Execute this command after all inbound queues are quiescent.
The Replication Server is quiescent if:
- There are no subscription materialization queues
- Replication Server has read 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 have been received from data servers
RSI normally empties its queue every 30 seconds.

Any user may execute this command.