OPICO VALLE DE SAN ANDRÉS
VALLE DE SAN ANDRÉS Nos quedaremos con tu corazón
ALTER
Sets or changes global configuration values for SDR. Global parameters are the default configuration settings for SDR.
parameter-and-value
ACCESSID { USER[ID] | (SU{PER[ID] }
specifies the user ID under which the DDL replication operations are performed, with the exception of CREATE TABLE or CREATE INDEX operations (see CREATEID { user-ID | user-name } below).
Setting the global ACCESSID to USER[ID] instructs the SDR updater to use the same user ID to perform the DDL operation on the backup as was used to perform the DDL operation on the primary system.
The default is SUPER[ID], which causes all DDL operations, except CREATE, to be performed under SUPER,SUPER.
ALTER [ GLOBAL ] parameter-and-value
parameter-and-value is
{ ACCESS[ID] { USER[ID] | SUPER[ID] } }
{ }
{ AUTOCREATECATALOG { ON | OFF } }
{ }
{ CREATEID { user-ID | user-name } }
{ }
{ CREATESECURITY “rwep” }
{ }
{ DDLCAPTURE
{ ENABLE[D] | DISABLE[D] | REQUIRE[D] | TEST[ING]} }
{ }
{ EMSCOLLECTOR [ $collector ] }
{ }
{ KEEPPHYSVOL { ON | OFF } }
{ }
{ NETWORK RDF-control-subvol, primary-node, backup-node }
{ }
{ RDFCONFIG { RDF-control-subvol | DEFAULT }
{ AUTO[MATIC] | MANUAL | NOREPL[ICATE] } }
{ }
{ RETENTION n { HOURS | DAYS | WEEKS } }
{ }
{ UNAUDITEDDDL { OFF | ON } }
{ }
SDR Commands ALTER
AUTOCREATECATALOG { ON | OFF }
specifies that SDR should automatically create catalogs on the backup system, whenever RDF indicates that a catalog is required. For automatic catalog creation, RDF must be configured to replicate data for the files in the catalog subvolume.
Automatic catalog creation is independent of any other SDR facility. RDF may be referencing a catalog due to reasons unrelated to an SDR DDL operation. The default is OFF.
CREATEID { user-ID | user-name }
sets the owning user ID of any SQL object being created.
The default owner is the user ID that created the primary object. CREATESECURITY “rwep”
sets the SECURE option of any SQL object being created.
DDLCAPTURE { ENABLE[D] | DISABLE[D] | REQUIRED | TEST[ING} controls the capture of SQL DDL operations on the primary:
ENABLE[D]
enables the capture of all SQL DDL operations, providing a. the SDR monitor is running, and
b. SDR is licensed and,
c. SDR has been INSTALLed in the SQL utilities. DISABLE[D]
disables the capture of SQL DDL operations. REQUIRE[D]
the capture of SQL DDL operations is enabled and, if for any reason the DDL operations cannot be captured by SDR, the DDL operations are not executed on the primary system.
If SDR aborts a DDL operation on the primary system, a message is logged to EMS to notify the user that DDL capture is REQUIRED, but an environmental problem is preventing SDR from capturing the DDL
operation.
Note. As a usage example, you are advised to set DDLCAPTURE to REQUIRED when you install an update to the SDR software, at least until the installation is completed on all the systems in the RDF network. See “Updating SDR Software” on page 2-8 for further details.
SDR Commands ALTER
TEST[ING]
disables the capture of DDL operations unless one of the following enablers is present:
°
the CLASS MAP DEFINE =_SDR_TEST DEFINE has been set or,°
an empty file named ENABLSDR is present in the default subvolumefor the process creator user id. EMSCOLLECTOR $collector
specifies a collector process name for all SDR EMS messages. The default collector is $0.
KEEPPHYSVOL { ON | OFF }
specifies that PHYSVOL specifications in CREATE and ALTER statements should always be retained, even if they lead to errors in replication.
The DEFAULT is ON.
NETWORK RDF-control-subvol, primary-node, backup-node
used for the replication of DDL operations performed on distributed tables or indexes, to provide SDR with the description of the RDF network nodes.
RDF-control-subvol is an RDF configuration in the format node[suffix- character].
primary-node and backup-node are the names of the primary and backup systems respectively
Specifying NETWORK is not required and is not recommended for RDF/IMPX installations, where SDR extracts the necessary network information from the RDF NETWORK configuration.
There is no SDR “master” network node. A complete description of the RDF network must be entered on every node, both primary and backup.
There can be no more than 31 NETWORK globals. RDFCONFIG { RDF-control-subvol | DEFAULT }
{ AUTO[MATIC] | MANUAL | NOREPL[ICATE] }
used to support parallel RDF configurations (most commonly production and test) that may share RDF protected volumes, to avoid disrupting the specified RDF configuration (most commonly production).
RDF-control-subvol is an RDF configuration in the format node[suffix- character].
DEFAULT applies to all RDF configurations that do not have an explicit RDFCONFIG setting.
SDR Commands ALTER
AUTOMATIC
The SDR Updater automatically replicates SQL DDL for the specified RDF configuration, subject to any other control such as HOLD, RELEASE and so on.
AUTOMATIC is the default. MANUAL
If a SQL DDL target object (table, index, so on) is protected by an RDF configuration, the SDR Updater enters a hold state to allow the user to manually examine and control replication. The user should issue a CANCEL or EXECUTE command to proceed and restart RDF updating. NOREPL[ICATE]
The SDR Updater does not replicate any SQL DDL operation for the specified RDF configuration and restarts RDF updaters immediately when the RDF updaters stop for the NSA Stop Update generated by SDR. Note that AUTOCREATECATALOG is not active when NOREPLICATE is configured.
RETENTION n { HOURS | DAYS | WEEKS }
sets the retention period for SDR Depot records that store captured DDL operations.
The minimum retention period is 24 hours. If the user sets it to a smaller value, SDR rounds it up to 1 day.
The maximum retention time is 60 days. The default is 1 week.
UNAUDITEDDDL { ON | OFF }
specifies how SDR will process DDL statements for unaudited tables.
If set to ON, SDR will replicate and apply DDL statements for unaudited tables, even if DML statements are not replicated by RDF.
The default is OFF
USERTRAN[SACTION] { ABORT | HOLD | [ASSUME]COMMIT }
specifies how SDR will process DDL statements executed under a user transaction.
ABORT
causes SDR to disallow the execution of a DDL statement within a user transaction. NonStop SQL already disallows the execution of many DDL statement within a user transaction; this further extends the prohibition to
SDR Commands CANCEL
When a DDL statement is attempted under a user transaction, SDR writes a message to the home terminal of the application program and to EMS and aborts the transaction, which causes the SQL statement to terminate with error -1353.
HOLD
causes SDR to write a message in the EMS log and wait for the user to issue an SDRCOM command to either EXECUTE or CANCEL the statement.
HOLD is the default. [ASSUME]COMMIT
causes SDR to take the optimistic view that the transaction will eventually be committed and to replicate the DDL statement to the backup system.
CANCEL
Instructs the SDR updater that manages the specified RDF configuration to restart the RDF updaters without executing a DDL operation that was previously attempted and did not complete.
Restarting the RDF updaters that are awaiting completion of the DDL statement replication means that RDF simply proceeds and consequently, the DDL statement is never replicated.
Certain SDR configuration or processing errors make it impossible to determine the information necessary to restart the RDF updaters. For example, an incomplete RDF or SDR network specification can make it impossible to restart updaters on all
participating network systems. In this case, CANCEL has no effect and you must use RDFCOM to restart the updaters.
RDF-control-subvol
the RDF configuration in the format node[suffix-character] that replicates the SQL object that is the target of the DDL operation.