Server, Database, and CDDS Status
You can control traffic in a server by quieting or activating:
• The whole server
• Specific target databases
• Specific CDDSs
To affect a running server, you must send an event to it.
Visual DBA and Performance Monitor: For more information, see the Raising Events at the Server Level topic in online help for Visual DBA or Visual Performance Monitor.
Replicator Manager: You can send an event from the Replication Monitor or from a terminal monitor. For more information, see
Send Database Event Window.
Servers, databases, or CDDSs can also be quieted by errors, depending on the error mode setting.
When you start a server, all databases and CDDSs are made active. You can, however, start a server in quiet mode by setting the Quiet Server (-QIT) flag as a startup parameter.
The flags that control server, database, and CDDS status are described below:
-NQT (Default)
An active server continually processes transactions for replication.
The Unquiet Server (-NQT) flag is primarily used on a server to resume propagation suspended with the -QIT flag.
-QIT
A quiet server ignores the activity in the replicated database and processes only the pending replication transactions when it receives a dd_go_server
n database event. When used in conjunction with the -EVT flag, the server also processes transactions on a periodic basis. For more information, see
-EVTn Flag--Use Event Timeout.
If the CDDS has QuietServer error mode and an error occurs, this flag is set against a server. Use the -NQT flag to activate the server.
-SGL
A single run server processes the pending replication transactions for its server number before it shuts down. This status is generally used to schedule the replication with the operating system’s job scheduling system.
-CLQ
If an error occurs that quiets a CDDS or database, the Clear Quiet Targets (-CLQ) flag resumes propagation. When
-CLQ is issued against a server, the server continues quiet; all quieted CDDSs and databases that the server is assigned to are activated for propagation.
Note: The value of this flag is stored in the replicator system catalogs; using the dd_set_servern event merely causes the replication server to update the value.
-QDBn
The Quiet Database (-QDBn) flag suspends propagation activity to database number n. This flag can be set using the dd_set_servern event or in response to an error (if the error mode QuietDatabase was set).
Note: The value of this flag is stored in the replicator system catalogs; using the dd_set_servern event merely causes the replication server to update the value.
Use the -UDBn or -CLQ flag with the dd_set_servern event to resume propagation activity to a quiet database.
-UDBn(default)
The Unquiet Database (-UDB) flag resumes propagation activity to a database after it is suspended with the Quiet Database (-QDB) flag or by an error (if error mode QuietDatabase was set).
-QCDn
The Quiet CDDS (-QCDn) flag suspends propagation activity to CDDS number n. This flag can be set using the dd_set_servern event or in response to an error (if the error mode QuietCDDS was set).
Note: The value of this flag is stored in the replicator system catalogs; using the dd_set_servern event merely causes the replication server to update the value.
Use the -UCDn or -CLQ flag with the dd_set_servern event to resume propagation activity to a quiet database.
-UCDn(default)
The Unquiet CDDS (-UCDn) flag resumes propagation activity to a CDDS after it was suspended with the -QCDn flag or by an error (if error mode QuietCDDS was set).
Note: The QDB, UDB, QCD, and UCD flags do not take effect immediately; instead, they prevent or allow propagation the next time the servers read transactions from the distribution queue.