Unaudited tables and indexes, Sqlci dup utility, Ddl replication – HP NonStop G-Series User Manual
Page 47: Sdr updater processes, Normal vs. takeover operations, Unaudited tables and indexes 4-7, Sqlci dup utility 4-7, Ddl replication 4-7, Sdr updater processes 4-7, Normal vs. takeover operations 4-7
SDR Operations
HP NonStop SQL DDL Replicator User’s Guide —545799-005
4-7
DDL Replication
Unaudited Tables and Indexes
SDR writes every DDL operation to a depot file, but it writes the SRU audit record only
if the target SQL object is audited. Since the SRU audit initiates SDR replication, DDL
for unaudited objects is not replicated. See
for options available to process DDL replication on unaudited tables.
SQLCI DUP Utility
The DUP command executes several internal DDL operations to create tables and
indexes and to alter table attributes. DDL for DUP operations are never captured or
replicated by SDR.
DDL Replication
The following paragraphs discuss topics relating to the replication of the captured DDL
statements to the backup system(s):
SDR Updater Processes
The SDR monitor is responsible for monitoring all RDF activity. It does so by
monitoring RDF events sent to collector $0. The SDR monitor also makes a periodic
check of RDF and eventually makes the proper adjustments, even if the RDF events
are not available. When the SDR monitor detects an active RDF subsystem, it starts an
SDR updater process on the RDF backup system.
The SDR updater monitors events sent to the EMS collector that is configured as the
RDF LOGFILE. Although RDF always sends events to both $0 and any configured
LOGFILE, some installations might have a filter to eliminate RDF events. The SDR
updater depends on analyzing RDF events for proper operation.
Although the SDR updater is started and managed from the primary RDF system, the
SDR monitor must also be executing on the backup system.
Each SDR updater manages a specific RDF configuration. By RDF configuration, we
refer to the configuration identified by an RDF control subvolume of format node[suffix-
character]. If there are multiple active RDF control subvolumes, the SDR monitor will
start multiple SDR updater processes, one for each control subvolume. For example, if
on system \PRIM there are RDF control subvolumes PRIMA and PRIMB, there will be
two SDR updaters on the backup system, one for PRIMA and one for PRIMB.
Normal vs. Takeover Operations
When RDF is operating in normal mode, the SDR monitor on the primary RDF system
manages the SDR updater on the backup system. When RDF is operating in takeover