HP Integrity NonStop J-Series - Manual (Page 106)

SQL DDL Statements
HP NonStop SQL DDL Replicator User’s Guide —545799-007
A-4
PHYSVOL References in Statements
SDR will translate catalog references even if catalog subvolumes are excluded in the
RDF configuration. They will be translated to the same subvolume name on the backup
volume. Note that the volume must be protected by RDF.
This does not apply to CREATE CATALOG and DROP CATALOG. Also,
AUTOCREATECATALOG will not create a catalog when the catalog subvolume is
excluded in the RDF configuration.
PHYSVOL References in Statements
Some DDL statements support the assignment of virtual volumes to a specific physical
volume, or PHYSVOL. When SDR processes PHYSVOL references, the RDF
configuration must contain the physical volumes in its volume table. Also, the virtual
and physical volume assignments on the backup system must mirror the primary
system. Otherwise, the translated SQL statement will fail.
If you do not require the replication of physical volume assignments on the backup
system, set the SDR global option KEEPPHYSVOL to OFF.
WITH SHARED ACCESS Clauses
Some DDL statements support, or even require, a WITH SHARED ACCESS clause.
The clause provides the ability to control the time at which a DDL operation is
committed, because the commit can disrupt application access to the database. Since
applications are not making transactional access to the backup database, SDR always
specifies COMMIT WHEN READY.
A SQL DDL statement containing a WITH SHARED ACCESS clause will normally
cause RDF to stop the updaters when it is safe to replicate the DDL statement on the
backup system. The RDF updater stop is identified by the name of the SQL object.
But, when SDR is actively capturing DDL statements, the normal RDF updater stop is
cancelled. Instead, SDR causes the RDF updaters to stop for all SQL DDL statements,
and specifies an SDR marker file name.