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
Managing RDF
HP NonStop RDF System Management Manual—524388-003
5-3
Recovering From File System Errors
Table 5-1. Recovery From File Modification Failures (RDF Event
700) (page 1 of 2)
File System Error Recovery Action
1 Check file integrity. The updater process skips the modify operation.
RDF reports error 1 if an updater receives a “record not found” error
while attempting to perform the operation.
2 An invalid operation occurred. An error 2 could be caused by a
variety of reasons.
For example, error 2 is returned if an application has a data file open
for shared write access and an updater then attempts to open that
same file for exclusive write access.
In any case, this is a critical error. You should stop RDF and
investigate. If you cannot determine the cause of the error and
remedy the situation, contact your service provider.
If an updater reports an error 2 while attempting to apply an audit
record, it skips that record and goes to the next. In this case, after
you correct the error condition, you must reinitialize RDF to a point
earlier than the record that caused the error, and then restart RDF.
10 Check the file integrity. This could mean either loss of data or
duplicated audit information. If data was lost, resynchronize the file. If
audit information was duplicated, then no harm occurred. The updater
process skips the modify operation.
11 Check the file integrity. This could mean either loss of data or
duplicated audit information. If data was lost, resynchronize the file. If
audit information was duplicated, then no harm occurred. The updater
process skips the modify operation.
16 Check file integrity.
30 through 37 If the problem persists, alter hardware configuration or perform system
tuning.
43 through 45 Provide more room for the file or extent by using FUP commands,
such as PURGE and ALTER MAXEXTENTS, or by compressing files.
You might need to issue a STOP UPDATE command.
50 through 58 Repair the device or clear the condition.
59 Check file integrity.
60 through 66 Repair the device or clear the condition.
71 Check the file integrity. This could mean either loss of data or
duplicated audit information. If data was lost, resynchronize the file. If
audit information was duplicated, then no harm occurred. The updater
process skips the modify operation.
100 Repair the device or clear the condition.
103 Repair the device or clear the condition.
120 through 121 Repair the device or clear the condition.