RDF System Management Manual
Table Of Contents
- RDF System Management Manual
- What’s New in This Manual
- About This Manual
- 1 Introducing RDF
- RDF Subsystem Overview
- RDF Processes
- RDF Operations
- Reciprocal and Chain Replication
- Available Types of Replication to Multiple Backup Systems
- Triple Contingency
- Loopback Configuration (Single System)
- Online Product Initialization
- Online Database Synchronization
- Online Dumps
- Subvolume- and File-Level Replication
- Shared Access DDL Operations
- EMS Support
- SMF Support
- RTD Warning Thresholds
- Process-Lockstep Operation
- Support for Network Transactions
- RDF and NonStop SQL/MX
- Zero Lost Transactions (ZLT)
- Monitoring RDF Entities With ASAP
- 2 Preparing the RDF Environment
- 3 Installing and Configuring RDF
- 4 Operating and Monitoring RDF
- 5 Managing RDF
- Recovering From File System Errors
- Handling Disk Space Problems
- Responding to Operational Failures
- Stopping RDF
- Restarting RDF
- Carrying Out a Planned Switchover
- Takeover Operations
- Reading the Backup Database
- Access to Backup Databases in a Consistent State
- RDF and NonStop SQL/MP DDL Operations
- RDF and NonStop SQL/MX Operations
- Backing Up Image Trail Files
- Making Online Dumps With Updaters Running
- Doing FUP RELOAD Operations With Updaters Running
- Exception File Optimization
- Switching Disks on Updater UPDATEVOLUMES
- 6 Maintaining the Databases
- 7 Online Database Synchronization
- 8 Entering RDFCOM Commands
- 9 Entering RDFSCAN Commands
- 10 Triple Contingency
- 11 Subvolume- and File-Level Replication
- 12 Auxiliary Audit Trails
- 13 Network Transactions
- Configuration Changes
- RDF Network Control Files
- Normal RDF Processing Within a Network Environment
- RDF Takeovers Within a Network Environment
- Takeover Phase 1 – Local Undo
- Takeover Phase 2 – File Undo
- Takeover Phase 3 – Network Undo
- Takeover Phase 3 Performance
- Communication Failures During Phase 3 Takeover Processing
- Takeover Delays and Purger Restarts
- Takeover Restartability
- Takeover and File Recovery
- The Effects of Undoing Network Transactions
- Takeover and the RETAINCOUNT Value
- Network Configurations and Shared Access NonStop SQL/MP DDL Operations
- Network Validation and Considerations
- RDF Re-Initialization in a Network Environment
- RDF Networks and ABORT or STOP RDF Operations
- RDF Networks and Stop-Update-to-Time Operations
- Sample Configurations
- RDFCOM STATUS Display
- 14 Process-Lockstep Operation
- Starting a Lockstep Operation
- The DoLockstep Procedure
- The Lockstep Transaction
- RDF Lockstep File
- Multiple Concurrent Lockstep Operations
- The Lockstep Gateway Process
- Disabling Lockstep
- Reenabling Lockstep
- Lockstep Performance Ramifications
- Lockstep and Auxiliary Audit Trails
- Lockstep and Network Transactions
- Lockstep Operation Event Messages
- 15 NonStop SQL/MX and RDF
- Including and Excluding SQL/MX Objects
- Obtaining ANSI Object Names From Updater Event Messages
- Creating NonStop SQL/MX Primary and Backup Databases from Scratch
- Creating a NonStop SQL/MX Backup Database From an Existing Primary Database
- Online Database Synchronization With NonStop SQL/MX Objects
- Offline Synchronization for a Single Partition
- Online Synchronization for a Single Partition
- Correcting Incorrect NonStop SQL/MX Name Mapping
- Consideration for Creating Backup Tables
- Restoring to a Specific Location
- Comparing NonStop SQL/MX Tables
- 16 Zero Lost Transactions (ZLT)
- A RDF Command Summary
- B Additional Reference Information
- C Messages
- D Operational Limits
- E Using ASAP
- Index
NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-3
Creating NonStop SQL/MX Primary and Backup
Databases from Scratch
Where catalog is the local catalog, node is the remote system where you want
the local catalog registered, and volume is where the local catalog is to be
registered on the remote system.
For example, the following command (if executed on the primary system) registers
the primary catalog on volume $DATA00 of the backup system:
REGISTER CATALOG pcat ON \bnode.$data00;
The following command (if executed on the backup system) registers the backup
catalog on volume $DATA00 of the primary system:
REGISTER CATALOG bcat ON \pnode.$data00;
4. Create the schema on the primary system.
If you do not use the LOCATION clause, NonStop SQL/MX will set the subvolume
itself. In that case, you must query NonStop SQL/MX to obtain the subvolume
name because the subvolume name is needed when creating the schema on the
backup system.
If you specify the LOCATION clause, the subvolume name must start with "ZSD"
and the entire name must be eight characters in length.
For example, if issued on the primary system the following command (without a
LOCATION clause) creates a schema called PCAT.SCH on the primary system:
CREATE SCHEMA PCAT.SCH;
If you omit the LOCATION clause, then, after creating the schema, you must use
the following query to obtain the subvolume of the schema (where you fill in the
correct node-name, schema-name, and catalog-name):
SELECT S.schema_subvolume
FROM NONSTOP_SQLMX_node-name.system_schema.schemata S,
NONSTOP_SQLMX_node-name.system_schema.catsys C
WHERE S.schema_name = 'schema-name' AND
C.cat_name = 'catalog-name' AND
S.cat_uid = C.cat_uid;
Note that node-name is a Guardian system name excluding the backslash (\).
In the following example, the node-name is PNODE, the schema-name is SCH,
and the catalog-name is PCAT.
SELECT S.schema_subvolume
FROM NONSTOP_SQLMX_PNODE.system_schema.schemata S,
NONSTOP_SQLMX_PNODE.system_schema.catsys C
WHERE S.schema_name = 'SCH' AND
C.cat_name = 'PCAT' AND
S.cat_uid = C.cat_uid;