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

Configuring SDR
HP NonStop SQL DDL Replicator User’s Guide—545799-005
3-6
Configuring SDR Replication
In cases where the table is created on the backup system by SUPER.SUPER, the
ownership or the table can be set to the userid that owns the table on the primary
system by specifying the GIVETOUSER option of CREATEID.
You can also specify a security string to add to CREATE TABLE, VIEW, and CATALOG
operations if none is explicitly specified, by setting the global parameter
CREATESECURITY.
Setting the User ID for Replicated DDL Operations
By default, all replicated DDL operations other than CREATE (see discussion above)
are performed under the super id.
You can choose instead to have the operations performed under the same user ID that
performed the operation on the primary system, by setting the global parameter
ACCESSID to USERID.
Automatic Catalog Creation
If a DDL operation references a catalog that does not exist on the backup, SDR can be
configured to create the catalog automatically, by setting the global parameter
AUTOCREATECATALOG to ON.
SDR creates a catalog automatically when audit records indicate that a catalog table is
being updated, but only if the primary catalog resides on a subvolume that is replicated
by RDF (included or, not excluded, in the RDF configuration).
When a catalog is updated on the primary system, the updated rows are placed in the
TMF audit trail. If RDF is configured to replicate updates in the catalog subvolume,
RDF requires that the catalog tables exist on the backup system. If they do not, then
the RDF updater stalls, issuing event 736 messages.
If AUTOCREATECATALOG is set, then the SDR updater detects that RDF is looking
for the catalog table and creates the catalog. SDR creates the catalog even if
DDLCAPTURE is DISABLED and the CREATE CATALOG was not captured.
Usage note for GIVETOUSER: Consider the following scenario:
•
You want the tables and catalogs on the backup system to be owned by the same user ID
as on the primary system but you also do not want the users on the backup system to
have access to the replicated tables because the backup system is also a development
system.
•
A SafeGuard ACL is created to prevent development users to access the backup
production tables.
•
Because of the SafeGuard setting, SDR cannot create the table under the original owner
and must create the objects under SUPER.SUPER.
GIVETOUSER instructs SDR to give the ownership of the replicated table or catalog to the
original owner after it has created the objects.