NonStop SQL DDL Replicator User's Guide (Update 6)

HP NonStop SQL DDL Replicator User’s Guide—545799-006
5-1
5 SDR Monitoring and Control
This section describes the commands available to query the status of SDR and control
its operations:
Checking Status

EMS Log

The SDR Log

STATUS Commands
Controlling Replication

Monitor-Level Commands

Updater-level Command
Checking Status
EMS Log
SDR sends numerous event messages to the EMS collector. The default collector is
$0, but you can specify a different collector by setting the EMSCOLLECTOR global
parameter to an alternate collector. Unlike RDF, SDR sends messages to a single
collector. RDF always sends events to $0 as well as an alternate collector.
The SDR monitor and updaters log informational events, such as monitor and updater
activity, action events that require operator intervention and critical events. All events
are logged in the EMS collector on the primary system. Consequently, it is
recommended you monitor the EMS log for SDR events, in the same manner you do
for RDF events.
To facilitate the monitoring of the EMS log, the SDR product subvolume contains the
EMS template and filter files ZSDRTMPL and SDRFLTR that restricts the event display
to SDR events.
For an example of how you can start an EMS distributor to display only SDR events,
see Start an EMS distributor
on page 2-4.
For your convenience, the SDR product subvolume also contains EMS template and
filter files ZCOMTMPL and COMFLTR that can be used to display RDF events in
addition to SDR events.
The SDR Log
The SDR log (SDRLOG) is a key-sequenced Enscribe file where replicated DDL
operations are recorded. SDRLOG resides on the backup system in the SDRSYSDB
subvolume.