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
Messages
HP NonStop RDF System Management Manual—524388-003
C-118
RDFCOM Messages
Effect. The configuration command fails.
Recovery. Determine why the communications path to this system is down and take
the appropriate recovery steps to bring it back up.
Cause. The specified primary system does not exist.
Effect. The configuration command fails.
Recovery. You must specify a valid primary system name.
Cause. RDFCOM is unable to reach the specified primary system.
Effect. The configuration command fails.
Recovery. Determine why the comm path to this system is down and take the
appropriate recovery steps to bring it up.
timestamp
is the shutdown timestamp to which the initialization was requested.
Cause. RDFCOM has searched the entire MAT currently on disk, but the timestamp
you specified in the INITIALIZE RDF command is earlier than the earliest audit
timestamp in the audit trail
Effect. RDF is not initialized.
Recovery. If all files of the MAT are currently on disk (for instance, the files from
AA000001 to the current audit file), then the specified timestamp is earlier than the last
time TMF was initialized. To recover, you need to reexamine the EMS log or the
OPRLOG for a later TMF shutdown point or stop TMF and use that shutdown point.
If the shutdown record is located in an audit file that is no longer on disk, you will need
to restore that file to disk, as well as all files between it and the latest file, and then
reenter the command. For example, if files AA000009 through AA000010 are currently
on disk, and the shutdown record is located in AA000007, then you must restore
AA000007 through AA000008 to disk. Alternatively, you can use a different TMF
shutdown point that is located in a MAT file still on disk, or you can stop TMF and use
that resulting shutdown point.
Specified network primary system <name> is not defined.
Specified network primary system <name> is unavailable.
Specified TMF shutdown timestamp at timestamp is earlier than
the earliest timestamp in the TMF MAT. Please examine the
OPRLOG for a correct TMF shutdown timestamp.