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-48
RDF Messages
Cause. This informational message is logged by an updater when it begins a restart
operation. The image file sequence number and the relative byte address within that
image file are included in the message.
Effect. An updater restart is performed under a variety of circumstances, such as a
failure in the primary CPU of the updater, a failure in the primary CPU of the
corresponding disk process, or various file errors. The reason for the updater restart
can be determined from previous messages. During an updater restart, file system
errors 10, 11, and 71 are not reported by the updater because they probably represent
database operations that have already been performed.
Recovery. Perform any corrective actions suggested by the preceding messages
(actions such as reloading the appropriate CPU, correcting the underlying file error
condition).
838
Cause. The RDFNET process has terminated unexpectedly.
Effect. This message is issued by the RDF monitor. The monitor sends an abort
request to all remaining RDF processes to stop RDF.
Recovery. Determine the reason why the RDFNET process stopped, correct that
problem, then restart RDF. If the problem persists, contact your service provider.
839
filename
is the name of the audit-trail file that could not be found.
Cause. The extractor was unable to find the designated audit-trail file.
Usually this occurs because TMF has purged the audit-trail file while RDF was
stopped. When RDF is running, RDF prevents TMF from purging audit-trail files until
the extractor has read them, even if the extractor is running far behind TMF (the
extractor has a large RTD value) and TMF has performed several rollovers. Use the
STATUS RDF command to see the extractor’s current RTD value.
Effect. The extractor tries to open the audit-trail file indefinitely unless an irrecoverable
error occurs on the file.
Recovery. Restore the audit-trail file from tape by using SNOOP RESTOREAUDIT.
If copies of the audit trail have not been maintained, then you will have to reinitialize
RDF, and resynchronize the primary and backup databases.
RDFNET process has terminated unexpectedly
Error - Audit-trail file is missing. File filename