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
Operating and Monitoring RDF
HP NonStop RDF System Management Manual—524388-003
4-25
Reading Log Messages
2. RDF then closes the log (if it is open). The log remains as configured.
The next time RDF needs to write a message to the log, RDF attempts to reopen the
configured log. If the error condition persists, RDF repeats the steps just described.
Examining RDF Messages
Previous RDF products directed their messages to a log device and a log file.
RDF/IMP and IMPX, however, direct their command, event, warning, and error
messages to an EMS collector in the form of fully-tokenized messages.
You can peruse messages in the EMS log on your terminal screen by using Viewpoint
or whatever other tool you normally use for monitoring $0. Note that when doing that,
however, you are dealing with the entire EMS log (not just RDF messages).
To isolate RDF messages from the rest of the EMS log, you can use the standard EMS
filter RDFFLTO to produce an intermediate entry-sequenced file which you then can
scan using the RDFSCAN utility.
As noted earlier in this section, when you access RDFSCAN, this utility displays
current information about the RDF message file, including the number of the last
record. This number, presented in the following format, indicates the size of the
message file so you can estimate where to begin your scanning:
File: $SYSTEM.RDF.RDFLOG, current record: 9454, last record: 9466
With RDFSCAN you can specify:
•
A starting point within the message file
•
The number of records to retrieve
•
Text to search for in the message file
RDFSCAN displays those RDF messages that meet the criteria you specify.
The following is a sample display for a primary system. (The column numbers in the
top line do not appear in the display, and are included only for reference. )
(1) (2) (3) (4) (5) (6)
2004/06/09 16:10:51 \LA $MON1 731 RDF Monitor Started
2004/06/09 16:11:08 \LA $Z333 774 RDF Local Extractor Started
Note. The record numbers reflected by RDFSCAN are approximate and might not exactly
match the record numbers that would be displayed by a FUP INFO RDFLOG, STAT command.