The Replication Server daemon threads shown in Table 4-1 perform miscellaneous tasks in the replication system.
Thread or daemon name |
Description |
|---|---|
Alarm daemon (dALARM) |
The alarm daemon keeps track of alarms set by other threads, such as the fade-out time for connections and the interval for the subscription retry daemon. |
Asynchronous I/O daemon (dAIO) |
The asynchronous I/O daemon manages asynchronous I/O to Replication Server stable queues. |
Connection manager daemon (dCM) |
The connection manager daemon manages connections to data servers and other Replication Servers. |
Recovery daemon (dREC) |
The recovery daemon takes care of various operations in connection with warm standby applications, routing, and recovery procedures. |
Subscription retry daemon (dSUB) |
The subscription retry daemon wakes up after a configurable timeout period (sub_daemon_sleep_time configuration parameter in the rs_config system table) and attempts to resume processing for subscriptions that may have failed. |
Version daemon (dVERSION) |
The version daemon activates briefly when the Replication Server is started for the first time after an upgrade. It communicates the Replication Server new version number to the ID Server. |
RS user thread |
The RS user thread manages connections from replicate Replication Servers during the process of creating or dropping subscriptions. See “Subscription materialization methods” on page 361 in the Replication Server Administration Guide Volume 1 for the data flow involved in creating and dropping subscriptions. |
USER thread |
A USER thread is created when a user logs in to a Replication Server to execute RCL commands. |
