The command admin who displays the states of all threads in the Replication Server, including DSI scheduler and executor threads. In the output of admin who, the DSI scheduler threads have the name “DSI” and DSI executor threads have the name “DSI EXEC.” If the DSI is suspended when Replication Server starts up, the output shows only one DSI executor thread, even if additional DSI executor threads are configured.
The command admin who, dsi shows the states of all running DSI scheduler threads and provides configuration values and other information about them. If a DSI scheduler thread exists for a database but does not appear in the output of admin who, dsi, use the resume connection command to restart the data server interface for the database. For a complete description of admin who, dsi output, see the Replication Server Reference Manual.
The states of DSI scheduler threads in the output of admin who and admin who, dsi are:
Active – the thread is starting, restarting after an internal error, or logging an exception to the RSSD.
Awaiting Command – the thread is waiting for a transaction to become available in the stable queue for the database. The queue contains no complete transaction at this moment.
Awaiting Wakeup – the thread is sleeping before it restarts. It sleeps for two minutes after an error that can be retried. During the two-minute interval, the cause of the error may disappear or the System Administrator may correct the problem. If the problem is corrected, the thread can restart without error after the sleep interval.
A failed transaction is retried when it causes a data server error that you assigned the retry_stop or retry_log option using the assign action command.
Awaiting Message – the thread has dispatched transactions to the DSI executor threads and is waiting for them to complete.
Suspended – the DSI connection has been suspended by a user command, by an error, or by a drop subscription or activate subscription command with the with suspension clause. This state appears only in admin who output.
Down – the thread has not been started. This state appears only in admin who output.
The states of DSI executor threads in the output of admin who are:
Active – the thread is starting, executing a transaction at the data server, logging an exception to the RSSD, or restarting after an internal error.
Awaiting Message – the thread is processing a transaction and is waiting for another thread to complete processing its transaction, or the thread is waiting to receive another statement from the Stable Queue Transaction interface (SQT).
Awaiting Command – the thread is waiting to receive another transaction from the DSI scheduler thread.
Down – the meaning of this state depends on the state of the DSI scheduler thread as follows:
If the DSI scheduler thread is Down, the DSI executor thread connection was suspended when the Replication Server was started, and the connection has not been resumed.
If the DSI scheduler thread is Active or Awaiting Wakeup, the DSI executor thread connection is recovering from a retryable error and is starting or restarting.
Suspended – the connection has been suspended by a user command, an error, or a drop subscription or activate subscription command using the with suspension clause.
A failed transaction does not cause the DSI connection to be suspended and is retried if the failed transaction caused a data server error that you assigned the retry_stop or retry_log option using the assign action command. For more information about the assign action command, see Chapter 3, “Replication Server Commands,” of the Replication Server Reference Manual.