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-73
RDFCOM Messages
RDFCOM Messages
The following pages list all messages generated by RDFCOM. These messages
appear on your terminal screen during an RDFCOM session. Alternatively, they can
be directed to another output device or file through the OUT command, issued during
an RDFCOM session or the OUT parameter entered in the RDFCOM command that
begins the session. The messages appear in alphabetic order by message text.
Cause. RDFCOM could not resolve an ambiguous timestamp after a change to Local
Civil Time (LCT) when the LCT was changed relative to Greenwich Mean Time (GMT).
In this situation, two LCTs map to the same GMT and it is impossible to determine the
correct intended time.
This problem typically occurs in Autumn, when the clock is set back from Daylight
Savings Time. If you specify an RDF initialization timestamp between 1:00AM and
2:00AM on that day, the intended time is ambiguous. Did you mean before the clock
was turned back or after? To eliminate this ambiguity, a specified RDF initialization
timestamp in this one-hour interval is reported as an error.
Effect. Initialization is aborted.
Recovery. Reinitialize RDF specifying a timestamp that is earlier than the ambiguous
time.
Cause. You issued a STATUS RDF command after a TAKEOVER command has
completed, but one or more updater processes had terminated prematurely and was
therefore unable to process all applicable image audit data.
Effect. The primary and backup databases are inconsistent.
Recovery. To determine which updaters terminated prematurely, examine the EMS
event log for error number 726. Then, reissue the TAKEOVER command.
Cause. You must specify the the PrimarySystem, BackupSystem,
RemoteControlSubvolume, and PnetTxVolume attributes for each Network record in
the configuration of your network master, but you are missing one or more or more of
these network attributes.
Effect. The configuration command fails.
Recovery. Set the missing fields and add the record.
Ambiguous timestamp for operation
A partial RDF TAKEOVER has completed
A required attribute for network master is missing