HP NonStop RDF System Management Manual for J-series and H-series RVUs (RDF 1.10) HP Part Number: 529826-009 Published: October 2011 Edition: J06.03 and subsequent J-series RVUs and H06.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About This Document...................................................................................19 Supported Release Version Updates (RVUs)................................................................................19 Intended Audience..................................................................................................................19 New and Changed Information in This Edition............................................................................
Online Dumps of the Backup Database.................................................................................49 Subvolume-Level and File-Level Replication.............................................................................49 Shared Access DDL Operations...........................................................................................49 Configurable Software Location...........................................................................................49 EMS Support..............
Re-Creating an Empty Database With an OBEY Command................................................64 Synchronizing Databases With SQLCI Commands.............................................................65 Synchronizing Databases With BACKUP and RESTORE Utilities...........................................66 Synchronizing Databases With FUP.................................................................................67 Synchronizing Partitioned Files......................................................
Setting Individual Process Attributes.................................................................................84 RDFNET Process.......................................................................................................84 Monitor Process.......................................................................................................84 Extractor Process......................................................................................................85 Receiver Process............
Reading Log Messages.....................................................................................................109 Examining RDF Messages............................................................................................109 ASAP..................................................................................................................................112 5 Critical Operations, Special Situations, and Error Conditions........................113 Recovering From File System Errors.....
Online Method of Resynchronizing the Primary Database.................................................139 Offline Method of Resynchronizing the Primary Database.................................................139 Reading the Backup Database (BROWSE versus STABLE Access)................................................140 Near Real Time Read Access to Updates on the Primary System.................................................140 Access to Backup Databases with Stable Access.................................
Different NonStop SQL Product Versions.........................................................................164 Moving Duplicated Tables and Files to the Backup System................................................164 Example of Synchronizing An Entire Database Online..........................................................165 Synchronizing Selected Database Portions Online.....................................................................166 Overview..................................................
Security Restrictions.....................................................................................................182 RDF State Requirement.................................................................................................182 Usage Guidelines.......................................................................................................183 Examples...................................................................................................................183 ALTER.........
INFO EXTRACTOR Command With OBEYFORM Option.............................................198 INFO MONITOR Command....................................................................................198 INFO RDF Command..............................................................................................198 INFO VOLUME Command.......................................................................................199 INFO PURGER Command.....................................................................
Security Restrictions.....................................................................................................214 RDF State Requirements................................................................................................214 Usage Guidelines.......................................................................................................214 Example....................................................................................................................215 SET PURGER....
Security Restrictions.....................................................................................................231 RDF State Requirement.................................................................................................231 Usage Guidelines.......................................................................................................231 Examples...................................................................................................................232 START UPDATE..
VALIDATE CONFIGURATION............................................................................................247 Where Issued.............................................................................................................247 Security Restrictions.....................................................................................................247 RDF State Requirement.................................................................................................247 Usage Guidelines.....
Summary.............................................................................................................................265 11 Subvolume-Level and File-Level Replication................................................266 INCLUDE Clauses.................................................................................................................266 EXCLUDE Clauses.................................................................................................................
Takeover Delays and Purger Restarts...................................................................................283 Takeover Restartability......................................................................................................283 Takeover and File Recovery...............................................................................................283 The Effects of Undoing Network Transactions.......................................................................
Consideration for Creating Backup Tables................................................................................316 Restoring to a Specific Location..............................................................................................317 Example.........................................................................................................................317 Comparing NonStop SQL/MX Tables.....................................................................................
SET RECEIVER.................................................................................................................335 SET TRIGGER..................................................................................................................335 SET VOLUME..................................................................................................................335 SHOW..........................................................................................................................
About This Document The Remote Database Facility (RDF) subsystem enables users at a local (primary) system to maintain a current, online copy of their database on one or more remote (backup) systems, protecting stored information from damage that might occur at the primary system. RDF accomplishes this by sending audit trail information, generated at the primary system by the NonStop Transaction Management Facility (TMF) product, over the network to the backup system.
New features in the RDF 1.10 manual • Updated the VALIDATE CONFIGURATION command in RDFCOM to include information on validation report generation support. • Added new error messages in Appendix C. Updates to the RDF 1.10 manual The following updates were performed in the RDF 1.10 manual: • Updated the RDFNETO attribute in RDF Process and Program Security Attributes (page 69). • Added the section Replicating purge operations with INCLUDE, EXCLUDE, INCLUDEPURGE, and EXCLUDEPURGE lists (page 269).
• Chapter 7 (page 158)describes how to synchronize entire databases or selected database volumes online. • Chapter 8 (page 176) and Chapter 9 (page 250) present the syntax of all RDFCOM and RDFSCAN commands, respectively, and give examples of these commands. • Chapter 10 (page 260) describes the triple contingency feature. • Chapter 11 (page 266) describes subvolume-level and file-level replication.
exit(-1); } Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. [ ] Brackets Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none.
Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( filename ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma.
Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic Text Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up.
%005400 %B101111 %H2F P=%p-register E=%e-register Related Information This manual belongs to the NonStop data management library of manuals. It is the only manual that fully and directly supports RDF.
Publishing History Part Number Product Version Publication Date 529826-003 NonStop RDF/IMPX 1.7 (T0346 and T0347) NonStop RDF/ZLT 1.7 (T0618) November 2005 529826–004 NonStop RDF/IMPX 1.8 (T0346 and T0347) and Lockstep Gateway (T1226) NonStop RDF/ZLT 1.8 (T0618) August 2007 529826–005 NonStop RDF/IMPX 1.9 (T0346 and T0347) and Lockstep Gateway (T1226) NonStop RDF/ZLT 1.9 (T0618) May 2009 529826–006 NonStop RDF/IMPX 1.9 (T0346 and T0347) and Lockstep Gateway (T1226) NonStop RDF/ZLT 1.
1 Introducing RDF This manual describes the Remote Database Facility (RDF) subsystem as implemented in version 1, update 11 of the HP NonStop RDF/IMP, IMPX, and update 10 of the RDF/ZLT independent products. Customers who install RDF 1.10 can use existing RDF configuration scripts provided the scripts are not making use of new functionality.
uses elements like before-images, after-images, and control records. In addition, you should also understand the TMF processes that perform backout, volume recovery, and file recovery. If you are not familiar with this information, you should read TMF Introduction.
In Figure 1, there are 20 audited volumes on the primary system ($D1 through $D20). Only volumes $D1 through $D15, however, are configured for RDF protection. Audit records for volumes $D1 through $D10 and $D16 through $D20 are sent to the master audit trail (MAT). The RDF master extractor process reads the MAT and sends audit records associated with volumes $D1 through $D10 to the RDF master receiver process on the backup system.
If the primary system is unexpectedly brought down because of a disaster, the outcome of some transactions might never be known, as illustrated in Table 1. Table 1 Audit Records at the Time of a Primary System Failure Primary database updates (Sequence in master audit trail Updates sent to the backup (Sequence in image trail file) file) TRANS100—Update 1 TRANS100—Update 1 TRANS100—Update 2 TRANS100—Update 2 . . . . . .
Features In providing backup protection for online databases, RDF offers many advantages: • Continuous Availability RDF maintains an online copy of your production database on one or more backup systems. If the primary system should go down, the backup database(s) will be consistent and you can resume your business processing on a backup system with minimal interruption and data loss. • Fault tolerance You can restart RDF after a system failure. Single processor failures do not bring the subsystem down.
Figure 2 RDF Topologies 32 • Supports master and auxiliary audit trail protection; RDF can protect all tables and files that are being audited by TMF, whether they are associated with the Master Audit Trail (MAT) or an auxiliary audit trail. • Subvolume and file replication In addition to volume replication, the RDF/IMP and IMPX products support replication of selected subvolumes and files.
• Economical processing RDF conserves resources at both sites. The extractor typically uses 1% of the resources used by the application on the primary and 4% of the Expand resources. On the backup system the cost of an updater process replicating an update operation is typically 15-25% of the original cost to do the operation on the primary system. On the primary system RDF uses just one process (the extractor) per audit trail to read and transmit audit records to the backup system.
• A NonStop SQL/MP DDL operation using the WITH SHARED ACCESS option is detected • An exception record is written 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. When you do that, you are dealing with the entire EMS log (not just RDF messages).
Figure 3 RDF Tasks to Maintain a Copy of a Database RDF Processes To accomplish its four major tasks, RDF runs different processes on the primary system and the backup system. These processes (the monitor and extractor on the primary system and the receiver, updaters, and purger on the backup system) divide these tasks as summarized in the following pages. The relationship of these processes to one another is illustrated in Figure 4. More details about their operation appear in“RDF Operations” (page 37) .
Figure 4 RDF Subsystem Processes Primary System Processes On the primary system: 36 • The monitor process coordinates most RDFCOM commands involving the main RDF processes (for example, start and stop). • Each extractor process reads an audit trail (the MAT or a particular auxiliary audit trail), filters out audit records not relevant to the backup database, transforms the audit record into an image record, and then transmits the image records to an associated receiver process on the backup system.
Backup System Processes On the backup system: • There is one receiver process for each configured extractor process. A receiver accepts the image records from its extractor, sorts them, and then writes them to the appropriate RDF image trail. • There is one updater process for each primary system volume being protected by RDF. Updater processes read image records from their RDF image trails and pass them to the disk process so that the disk process can perform the logical REDO operations.
Figure 5 Extractor Process Operation Reading large amounts of data from the MAT, the extractor process stores the following records for subsequent transmission to the backup system: • TMF control records ◦ All transaction state records ◦ TMP control point records ◦ TMF shutdown records ◦ File-incomplete records ◦ File-complete records ◦ Stop-RDF-Updater records • Redo audit records for RDF protected files (generated by applications) • Undo audit records for RDF-protected files (generated by
either for block splits or during FUP RELOAD operations, and all audits generated by the RDF updaters. The extractor always tries to fill the buffer to be sent to the receiver. The buffer never contains partial records; if the buffer is nearly full and the next record to be transmitted does not fit in its entirety, the extractor transmits the current buffer and puts that next record at the beginning of the next buffer. The extractor never waits for more than one second to send data to the receiver.
Sorted Image Trails RDF maintains its image data on disk volumes specified during RDF configuration. On each of these volumes, the collection of files that contains image data is known as an image trail; that is, there is one image trail per individual image trail volume. The standard image trail used by RDF, called the master image trail, contains the transaction status records that hold key information about whether a transaction has committed or aborted.
With sorted image trails, the activity of any one image file typically remains so low that it can be stored on the same disk volumes as the main database with no significant I/O impact. This approach is not recommended, however, if you require very high RDF performance or if RDF is running with the UPDATE option turned off; in this case, the image trails could eventually fill the volume; in such cases, it is best to have volumes exclusively dedicated to the image trails.
• Issues a logical REDO request to the disk process (during the normal forward pass over the image trail) for each update associated with its volume. • Issues logical UNDO requests to the disk process when backing out changes associated with transactions that need to be undone during RDF takeover or stop-update-to-timestamp operations. • Bundles the REDO and UNDO requests into batch TMF transactions, the duration of which is specified by the UPDATERTXTIME configuration parameter.
Each updater maintains a file status table to keep track of the files it has open. An updater closes any database file that has not been updated recently. Updaters also close database files when a STOP RDF or STOP UPDATE command is issued, or when the updater restarts because of error conditions. Additionally, if you alter the updater's OPENMODE while UPDATE is ON, then the updater closes all its file and then reopens them with the new OPENMODE.
Furthermore, because updates to the backup database are applied by logical REDO/UNDO operations, alternate key files and NonStop SQL indexes are not affected by an update to a file or table. Alternate key files or NonStop SQL indexes are updated independently as a consequence of the individual audit records generated on the primary system by TMF software. NOTE: You must be sure that volumes on the primary system containing alternate key files and indexes are protected by RDF.
Second, because considerable checking must be done across all trails to determine what files can be purged based on what transactions might be represented in the various files on the various image trails, the purger process performs this task. The purger process is a restartable process pair that runs on the backup system (it is started during START RDF and runs even when the updaters are stopped; image files are purged, however, only when updating is enabled).
Example 2 Chain Replication System \A System \B System \C RDF Subsystem 1 Primary DB 1 ---------> Backup DB 1 Primary DB 2 ----------> Backup DB 2 RDF Subsystem 2 Thus, system \B is both the backup system in RDF subsystem 1 and the primary system in RDF subsystem 2.
committed update of your application. Additionally, Primary DB 1 and Backup DB 1 are no longer in synch. Even though the updater on \B had its transaction aborted, that updater will re-apply the application update to Backup DB 1. When done, Primary DB no longer has the update, but Backup DB 2 does. Although this example describes a reciprocal configuration, the same basic problem can happen with chain replication.
monitor process. In this way, Expand problems affecting one configuration might not necessarily affect the others (depending on the configuration). RDF Control Subvolume The INITIALIZE RDF command includes a control subvolume suffix parameter (SUFFIX char), where char is an alphanumeric character. If you include this parameter, the RDF control subvolume on $SYSTEM will be the local (primary) system name without the backslash and with the specified character appended to it.
set of disks can be replicated to another set of target disks to provide a copy of the live database. There are two operational considerations unique to this environment: • The updaters operate in transaction mode, which means you should not stop TMF before stopping RDF. • The RDF takeover operation cannot be performed unless you manually stop the monitor and extractor processes before issuing the TAKEOVER command or include the ! option in the TAKEOVER command.
You should place the RDFCOM component on $SYSTEM.SYSTEM, or you must add the new software location to your TACL search-subvolume list. EMS Support RDF/IMP, IMPX, and ZLT all support the Event Management System (EMS). They direct their command, event, warning, and error messages to an EMS collector in the form of fully-tokenized messages. You can view messages in the EMS log online using Viewpoint or any other tool you normally use for monitoring $0. When you do, so you are perusing the entire EMS log.
RDF and NonStop SQL/MX RDF can replicate NonStop SQL/MX user tables and indexes as well as NonStop SQL/MP objects and Enscribe files. For information about this capability, see Chapter 16 (page 307). Zero Lost Transactions (ZLT) Zero Lost Transactions (ZLT), which is available only with the RDF/ZLT product, is a functional capability that uses mirrored disks to guarantee that no committed transactions on the primary system will be lost in the event of an RDF takeover by the backup system.
2 Preparing the RDF Environment Before RDF can be run on a NonStop system, the system configurations and user applications must meet certain RDF requirements. This chapter explains how to prepare each system for RDF installation and operation, ensuring that all these requirements are met and that you understand the RDF product’s restrictions.
Sizing the RDF configuration is a complex task that is best carried out by HP personnel. Those personnel can assist you in configuring and sizing your RDF environment using tools and utilities designed and developed as part of the RDF Professional Service. Contact your service provider for further details.
1. Enter a FUP INFO command for the current TMF MAT and record the end-of-file (EOF) value; for example: FUP INFO $AUDIT.ZTMFAT.* CODE EOF LAST MODIF OWNER RWEP TYPE REC BLOCK $AUDIT.ZTMFAT AA000003 134 11292672 10:05 -1 GGGG 2. Enter a FUP INFO command for the current MAT 5 minutes later and record the EOF value; for example: FUP INFO $AUDIT.ZTMFAT.* CODE EOF LAST MODIF OWNER RWEP TYPE REC BLOCK $AUDIT.ZTMFAT AA000003 134 11653120 10:10 -1 GGGG 3.
Table 3 Software Requirements (continued) Software Requirement Communications The RDF/IMP, IMPX, and ZLT products use Expand software to connect the primary system to the backup system. Operating System On the primary and backup systems, the installed release version update (RVU) of the operating system must be supported. TMF Subsystem On both the primary and backup systems, the installed RVU of the TMF subsystem must be compatible with the installed RVU of the operating system.
if you stop RDF. Audit trail pinning is lost if you stop TMF. See also the description of the UNPINAUDIT command in Chapter 8 (page 176). You can control when TMF dumps an audit trail by configuring TMF for dump to tape. For example, when configured with a tape dump process, TMF issues a prompt for the operator to mount a tape when TMF is ready to dump and purge an old audit trail file.
• Copies of NonStop SQL views on the backup systems • Placement of partitioned Enscribe files and NonStop SQL tables Audited Files Per Volume on Primary System The RDF updater process has a limit on the number of database files it can have open concurrently on a volume - 3,000. Therefore, when you set up your database on your primary system for RDF protection, you should ensure that you do not have more than 3,000 audited files on any single volume that you want replicated.
you might want to replicate $CAT.DSMCAT.* on the primary system to $DATA.DSMCAT.* on the backup system. In that way replication of the DSM Tape Catalog and related files from the primary to the backup system does not affect the DSM Tape Catalog and related files in $CAT.DSMCAT.* on the backup system.
Replicating Database Operations Database administrators preparing to work with RDF should be aware of considerations concerning: • NonStop SQL Data Definition Language (DDL) operations • NonStop SQL DDL operations with Shared Access • Enscribe file-label modifications • Purge operations • Partitioned files • Temporary disk files NonStop SQL DDL Operations Although RDF replicates NonStop SQL Data Manipulation Language (DML) operations, it does not replicate NonStop SQL Data Definition Language (D
Temporary Disk Files File creation, modification, and updates are not replicated for audited temporary disk files. All audit data is filtered out by the extractor on the primary system for file names of the form $volume.#nnnnnnn. A filename that begins with # (pound sign) indicates a temporary disk file; this type of file name is returned when only the volume name is specified in a call to the file-system CREATE procedure or FILE_CREATE_ procedure.
Configuring an SMF Environment on the Backup RDF System RDF supports the replication to SMF logical volumes on the backup system, with the following restrictions: • When replicating to an SMF logical volume, the logical volume must belong to an SMF pool that contains 15 or fewer physical volumes, hence each updater can apply audit to up to 15 physical disks. • The RDF/IMP product limits the total number of physical or virtual UPDATE volumes to 255.
3 Installing and Configuring RDF After preparing your system configurations and user applications to meet RDF requirements, you are ready to install and configure RDF. This chapter, which is intended for system managers, system analysts, and database administrators, describes how to do these tasks.
Preparing the Tables and Files Now prepare your tables and files. Separating NonStop SQL Tables It is recommended that you avoid registering NonStop SQL tables protected by RDF in the same catalogs as tables that are not protected by RDF. Separating protected tables from unprotected ones simplifies the comparison of primary system catalogs with backup system catalogs.
• All views and indexes dependent on base tables protected by RDF • All program files for applications that use any base tables protected by RDF if you want the applications to run at the backup site after an RDF takeover operation The backup system should also have copies of the following files in case an RDF takeover operation is necessary: • OBEY command files and TACL scripts containing NonStop SQL/MP or NonStop SQL/MX DDL commands that define the database • SQLCI or MXCI report definitions To m
1. 2. 3. Place the database creation commands in either an EDIT (command) file or TACL macro or routine. See the TACL Reference Manual for more information. Through the TACL command interpreter, issue an OBEY filename command or run the macro to create the primary database. Copy the command file or TACL macro to the backup system. Now do the following on the backup system: • Change any system references in the command file or TACL macro from the primary system name to the backup system name.
5. Enter CREATE CONSTRAINT commands for any constraints that values in particular columns of the table must satisfy: CREATE CONSTRAINT EMPNUM_CONSTRNT ON =EMPLOYEE CHECK EMPNUM BETWEEN 1 AND 99999; 6. Create the index for the NonStop SQL/MP table on the primary system: CREATE INDEX =EMPLNAME ON =EMPLOYEE( LAST_NAME, FIRST_NAME ); 7.
The next examples of BACKUP and RESTORE commands show how to copy all files from the primary system volumes $DATA01, $DATA02, $DATA03, and $DATA04 to the magnetic tape device named $TAPE and how to restore these files to volumes of the same name on the backup system. You must include the AUDITED parameter in both the BACKUP and RESTORE commands. BACKUP $TAPE,($DATA01.*.*,$DATA02.*.*,$DATA03.*.*, $DATA04.*.*), AUDITED RESTORE $TAPE,($DATA01.*.*,$DATA02.*.*,$DATA03.*.*, $DATA04.*.
Cache for RDF IMAGETRAILS and UPDATER UPDATEVOLUMES When you have determined the volumes you wish to use for Imagetrails and Updatevolumes, you should configure several thousand 4k blocks of cache for each volume. This will considerably increase the performance of the receiver and updaters. Installing RDF The RDF/IMP, IMPX, or ZLT software, and all related documentation, is distributed on three independent product release compact disks (CDs).
RDF/ZLT (T0618) Product Components The release CD includes the following components for the RDF/ZLT product: RDF/ZLT The RDF/ZLT enabler module Readme The software documentation file To use the RDF/ZLT product, you must purchase both RDF/IMPX and RDF/ZLT (two separate CDs), install RDF/IMPX, and then install RDF/ZLT.
Table 4 RDF Process and Program Security Attributes (continued) Program Name Run Under a Specific Logon ? LICENSE Required for Object File? MD5SRVO NO NO RDFCOM YES; 255,nnn + YES RDFEXTO YES ++ YES RDFMONO YES ++ YES RDFNETO YES ++ YES RDFPRGO YES ++ YES RDFRCVO YES ++ YES RDFSCAN NO++++ NO RDFSNOOP YES +++ YES RDFUPDO YES ++ YES READLIST NO NO RDIMAGE YES ++ YES + RDFCOM operational commands require super ID group access; however, INFO and STATUS commands can be issu
• RDFRCVO. The RDF receiver program opens the image files in privileged mode and must be licensed with FUP or by running the RDFINST macro. RDFRCVO can be owned by any user ID. • RDFSCAN. The RDFSCAN program contains no privileged calls or privileged code and need not be licensed. RDFSCAN can be owned and run by any user ID. • RDFSNOOP. The RDFSNOOP program opens the image files in privileged mode and must be licensed with FUP or by running the RDFINST macro. RDFSNOOP can be owned by any user ID.
If TMF was not running previously on the backup system, after you have installed TMF you must use TMFCOM to issue a START TMF command and one or more ADD DATAVOLS commands to add to the TMF configuration all disk volumes to be used by the RDF updater processes.
For complete information about the INITIALIZE RDF command, see the description of the INITIALIZE RDF command in Chapter 8 (page 176). Initializing RDF To a TMF Shutdown Timestamp If TMF was running previously on the primary system and did not need to be initialized and configured, you can initialize RDF to a timestamp that reflects the time of the last TMF shutdown. This initialization is typically used when one stops TMF in order to initialize RDF to that TMF stop location.
Determining a Valid inittime Value When using the INITTIME parameter without the NOW clause, it is important that you specify a valid inittime value. To do so, first issue a STATUS RDF command and take note of the highest updater RTD time. Then round that RTD time up to the next higher minute (0:43 becomes 1:00, 1:27 becomes 2:00, 3:04 becomes 4:00, and so forth). Finally, subtract that rounded-up time from the current system time shown in the status display.
database. In this particular case, the database is not corrupted, but data corruption could happen for other NonStop SQL/MP or NonStop SQL/MX DDL SHARED ACCESS operations.
6. 7. Install the new RDF software in a different volume.subvolume from that housing the current version of RDF that is running. For example, if you are upgrading to T0346ABS, you might specify $system.rdfabs. Run $system.rdfabs.RDFCOM and initialize a new RDF configuration, using: • The suffix parameter (such as suffix "a") • The INITTIME parameter, using the timestamp calculated in the preceding example (11AUG2008 05:24). Initialize RDF, backupsystem \RDF06, suffix a, inittime 11AUG2008 05:24 8. 9.
Configuring RDF For RDF to operate correctly, you must establish values for the following sets of attributes in the RDF configuration file: • Global attributes that apply across RDF • Attributes that apply to image trails • Attributes that apply to triggers • Network configuration record attributes • Process attributes that apply to the individual RDFNET, monitor, extractor, receiver, purger, and updater processes In addition to the configuration file on disk, RDFCOM maintains a copy in memory.
Setting Global Attributes The SET RDF command establishes values for global attributes that apply either to the entire RDF system or to all updater processes. These attributes and their default values are: • LOGFILE $0 • UPDATERDELAY 10 (seconds) • UPDATERTXTIME 60 (seconds) • UPDATERRTDWARNING 60 (seconds) • UPDATEROPEN PROTECTED • SOFTWARELOC $SYSTEM.
RDF updaters operate in transaction mode. Updater transactions are essentially long-running transactions that pin audit trail files on the backup system and can affect the duration of backout operations if an updater transaction aborts for any reason. The default value is recommended for RDF environments with heavy updater activity (aggregate updater throughput greater than 300 kb/second). Raising the tx-time in such environments might adversely affect TMF performance on the backup system.
When set to ON, the RDF subsystem provides database consistency for network transactions that were replicated to other backup databases by other RDF subsystems. When set to ON, you must either have the NETWORKMASTER attribute for the same system also set to ON or have another system configured as the network master. NETWORKMASTER Attribute The NETWORKMASTER attribute specifies whether the particular system is the master of the RDF network.
OWNER Attribute The OWNER attribute specifies a user ID under which all RDF processes will always run. This global configuration parameter provides functionality whereby any super ID group user ID can start and stop RDF. To illustrate this functionality, imagine ten users are responsible for managing a particular RDF configuration and that SUPER.RDF is configured as the OWNER. Instead of providing all ten users access to the SUPER.
rates for RDF-protected data on a given audit trail are generally in the range of 1 to 3 megabytes of audit per second, the number of updaters you need does not exceed 30, and you normally run with Update ON, you may be able to configure one image trail per updater and place that imagetrail on that updater's UPDATEVOLUME. You should have sufficient disk space to hold both your database files as well as the image trail.
Setting Network Configuration Record Attributes Use SET NETWORK and ADD NETWORK commands to configure the following network configuration record attributes: • PRIMARYSYSTEM system-name • BACKUPSYSTEM system-name • REMOTECONTROLSUBVOL subvolume-name • PNETTXVOLUME volume-name If you are configuring the network master RDF subsystem, you must include a network configuration record for every RDF subsystem in the RDF network (including the network master itself).
Setting Individual Process Attributes Having set the global attributes, you are now ready to set the parameters that apply to individual RDF processes: the RDFNET, monitor, extractor, receiver, purger, and updater processes. RDFNET Process Use SET RDFNET and ADD RDFNET commands to configure the following RDFNET attributes: • CPUS primary-CPU : backup-CPU • PRIORITY • PROCESS The CPUS attribute specifies the processors in the primary system in which the RDFNET process will run.
Extractor Process Use SET EXTRACTOR and ADD EXTRACTOR commands to configure the following extractor parameters: • ATINDEX • CPUS primary-CPU : backup-CPU • PRIORITY • PROCESS • RTDWARNING • VOLUME The ATINDEX attribute specifies an integer value from 0 through 15 specifying the TMF audit trail on the primary system with which the extractor is associated. 0 specifies the MAT. 1 through 15 specify auxiliary audit trails AUX01 through AUX15. The default is 0.
• RDFVOLUME • EXTENTS • FASTUPDATEMODE The ATINDEX attribute specifies an integer value identifying a configured TMF audit trail on the primary system. 0 specifies the MAT. 1 through 15 specify auxiliary audit trails AUX01 through AUX15. The default is 0. For each configured extractor, there must be a corresponding receiver with the same ATINDEX value. For information about protecting auxiliary audit trails, see Chapter 13 (page 276).
]SET RECEIVER EXTENTS (3000,3000) ]ADD RECEIVER You cannot start RDF until you have configured a master receiver process. You can issue ADD RECEIVER commands only when RDF is stopped. Purger Process Use SET PURGER and ADD PURGER commands to configure the following purger attributes: • CPUS primary-CPU : backup-CPU • PRIORITY • PROCESS • RETAINCOUNT • PURGETIME The CPUS attribute specifies the processors in the backup system in which the purger is to run.
• EXCLUDEPURGE • INCLUDEPURGE You must configure an updater process for each primary system volume to be protected by RDF. The ATINDEX attribute specifies an integer value from 0 through 15 specifying the audit trail on the primary system to which the data volume being protected is mapped. 0 specifies the MAT. 1 through 15 specifies auxiliary audit trails AUX01 through AUX15, respectively. The default is 0. The CPUS attribute specifies the processors in the backup system in which the updater will run.
You must configure all updaters to use secondary image trails, thereby leaving the RDFVOLUME (master image trail) exclusively for use by the master receiver (at index 0). Creating a Configuration Command File You can use the INFO * command with the OBEYFORM attribute to create a configuration command file quickly and easily from an existing RDF configuration: 1. Redirect the output of the RDFCOM session from your terminal to the configuration command file by issuing an appropriate OUT command.
Starting RDF There are two ways to start RDF: with updating enabled and with updating disabled. If updating is enabled, the updaters begin updating the backup database immediately. If updating is disabled, they do not (but the extractor and receiver continue to work normally). The default is to start RDF with updating enabled.
4 Operating and Monitoring RDF To operate and monitor RDF, you enter commands through two online utilities: the RDFCOM and RDFSCAN interactive command interpreters. Through these utilities, you initiate communication with RDF, request various RDF operations or information displays, and terminate communication with the subsystem.
IN command-file specifies a command file from which RDFCOM commands are to be read. RDFCOM reads 132-byte records from the specified file until it encounters either the end-of-file mark or an EXIT command. If you do not specify the IN option, TACL automatically supplies the name of its current default input file—usually the terminal from which you issued the RDFCOM command. Typically, it is very useful to have your RDF configuration commands specified in a text file.
For example, to start a session on a primary system named SANFRAN, you would enter the following command (assuming that no suffix character was specified in the INITIALIZE RDF command): >RDFCOM SANFRAN If the suffix character “3” was specified in the INITIALIZE RDF command, then you would enter the following command: >RDFCOM SANFRAN3 When RDFCOM starts, it searches the specified control-subvolume on $SYSTEM of the local system for the RDF configuration file to open.
communication with RDFCOM by entering the operating system command PAUSE at the TACL prompt. • If you press BREAK when an RDFCOM command that displays information (such as STATUS RDF) is in progress, RDFCOM terminates execution of this command and prompts you for another one. • If you press BREAK when an RDFCOM command that changes the RDF configuration or status (such as ALTER RDF) is in progress, RDFCOM continues to execute this command while immediately prompting you for another one.
To run RDFCOM and execute the commands in this file, supply the command file name in the IN option of the command to start RDFCOM: 4> RDFCOM /IN RDFSET/ control-subvolume When it uses a command file in this way, RDFCOM works in batch mode: RDFCOM begins the session, reads and executes each command from the command file, and displays the associated output at your terminal.
backup system. You have stopped TMF and RDF, you have reinitialized and reconfigured TMF, and you want to reinitialize, reconfigure, and restart RDF. Recall that before you can initialize RDF you must delete the control subvolumes on both primary and backup systems. These are executed by the first two commands in the TACL obey file above. The next command initializes RDF, specifying that the default system (\BOSTON) is your primary system and \SF is your backup.
RDF Subsystem PRIM2 \PRIM2 ------------------> \BACK2 RDF Subsystem PRIM3 \PRIM3 ------------------> \BACK3 Now suppose these RDF subsystems are running as an RDF network, you have lost PRIM1, you have stopped the applications on PRIM2 and PRIM3, and you want to execute the takeover commands from a single obey file to be executed on BACK1. Here are the commands you would put in the obey file. Assume that you have put RDFCOM on $SYSTEM.SYSTEM on each node and licensed it. \BACK1.$SYSTEM.
Table 5 RDFCOM Configuration Commands (continued) Command Object Function SET RDF; MONITOR; EXTRACTOR; RECEIVER; VOLUME; IMAGETRAIL; PURGER; RDFNET; NETWORK; TRIGGER; Adds option values to the configuration memory table for the specified process. SHOW RDF; MONITOR; EXTRACTOR; RECEIVER; IMAGETRAIL; VOLUME; PURGER; RDFNET; NETWORK; TRIGGER; Lists current option values from the configuration memory table for the specified process.
Table 7 RDFCOM Utility Commands Command Object Function EXIT -- Terminates an RDFCOM session. FC -- Enables you to edit (fix) a previously issued command. HELP {ABBREVIATIONS } {ALL } {command Displays help text for commands and messages. } {message-number} HISTORY -- Displays the 10 most recently issued RDFCOM commands. OBEY filename Causes RDFCOM to read commands from the specified command file. OPEN control-subvolume Sets the RDF control subvolume to $SYSTEM.
{ { { { { { PURGER RDFNET NETWORK TRIGGER trigger-type VOLUME $volume $volume } } } } } } Cannot be performed with RDF running. Only a user in the SUPER group can execute this command.
In response, RDFCOM displays the following information: ------------------------------------------------------------| 715 Primary Stopped | ------------------------------------------------------------Cause: The primary process of a NonStop process pair has stopped. This probably was the result of an operator inadvertently issuing a STOP command from TACL. Effect: The backup process takes over, but not in fault-tolerant mode, until the primary process can be re-created.
Enter the RDFSCAN function you want: To begin an RDFSCAN session and open the file $SPOOL.SANFRAN.RDFLOG for scanning, enter: >RDFSCAN $SPOOL.SANFRAN.RDFLOG RDFSCAN displays the following: RDFSCAN - T0346A06 - 14MAR04 (C)1988 Tandem (C)2004 Hewlett Packard Development Company, L.P. File: $SPOOL.SANFRAN.
The complete syntax for all RDFSCAN commands appears in Chapter 9 (page 250). You can abbreviate the command name by entering only the first character (such as L for List) or any number of the leading characters (such as DIS for Display). You can use either uppercase or lowercase letters.
Enter the next RDFscan function you want: HELP INTRO In response, RDFSCAN displays: RDFSCAN is a utility for quickly scanning the RDFLOG file. When you run RDFSCAN it calculates the last-record-number and displays it for you. You can then selectively list (display) various portions of the file. You can set the "current-record-pointer" via AT number. Then you can LIST count records in the file starting at number.
when the STATUS RDF command was issued. The second line specifies the fully-qualified name of the control subvolume. RDF States The third line specifies the current state of the subsystem; any of the following entries are possible: Table 9 RDF States Status Description Normal RDF running with Update On Normal - Update Stopped RDF running with Update Off Start Update Pending RDF was running with Update Off, Update was just turned On, but one or more updaters have not yet started.
are associated with the MAT, while the extractor $$REXT1 and receiver $RRCV1 are associated with auxiliary audit trail AUX01. Because of insufficient space, however, ATINDEX values are not displayed explicitly for updaters. To determine the ATINDEX value of a particular updater, see the ATINDEX value of the updater's specific image trail.
• Volume and Seqnce together specify a file associated with each process: The monitor entry reflects the name of the MAT file to which TMF is writing ($AUDIT.ZTMFAT.AA000056 in this example). Each extractor entry reflects the name of the TMF audit trail file that it is reading ($AUDIT.ZTMFAT.AA000056 for the master extractor and $DATA17.ZTMFAT.BB000004 for the auxiliary extractor in this example). The master receiver entry reflects the name of the master image trail file ($MIT.RDF04.
When RDF is not running, the STATUS RDF report indicates why. For example, the report might indicate that the subsystem has never been started, or that it has crashed. The report also indicates where processing resumes in the TMF audit trail when RDF is restarted.
To redirect messages from the current EMS log to the log named $EMSC (on the control subvolume CHICAGO), enter: ]ALTER RDF LOGFILE $EMSC The specified collector must reside on the local system. For example, if you are in an RDFCOM session on the system \SANFRAN, you cannot specify something like \CHICAGO.$EMSC as the log. For more information about the EMS log, see Chapter 1 (page 27), Chapter 3 (page 62), Chapter 8 (page 176), and Chapter 9 (page 250).
] HELP 906 This command returns the following: ----------------------------------------------------------------| | | 906 Process creation error ,file | | | ----------------------------------------------------------------Cause: The process encountered an error while attempting to create an RDF process.
In the preceding displays, the individual columns present this information: (1) Date-—is the date the message occurred, as reflected on the sending system. (2) Time—is the time the message occurred, as reflected on the sending system. (3) System—is the name of the system where the RDF process to which this message pertains is running. (4) RDF Process—is the name of the RDF process to which the message pertains. (5) Message Number—is the number that identifies the RDF message and its meaning.
ASAP HP's NonStop ASAP product provides in-depth monitoring of the RDF subsystem. It monitors the availability and status of all RDF components and also monitors how RDF is performing, in real-time and historically. ASAP lets a user set goals on key properties like RTD time and alerts when goals aren't met using a variety of alerting mechanisms. It also supports automated actions to recover from common problems without operator intervention.
5 Critical Operations, Special Situations, and Error Conditions When running RDF, there are a number of critical operations and situations that need careful consideration. Understanding all aspects of these operations and situations is essential. Understanding critical operations ensures that you perform said operations correctly, quickly, and efficiently. Understanding critical situations and error conditions ensures that you achieve resolution as quickly as possible.
and general recovery procedures), see the file-system information in the Guardian Procedure Error and Messages Manual. Some errors involving one or more updaters might require you to resynchronize certain files; see the EMS event log for further information. Any error that cannot be explained should be reported to your service provider.
Table 10 Recovery From File Modification Failures (RDF Event 700) (continued) File System Error Recovery Action 190 Repair the device or clear the condition. 200 through 231 Repair the device or clear the condition. 707 Enable the volume for TMF transaction processing. Table 11 lists the file-system error numbers and recovery actions for RDF event 705, which reports file-opening failures.
Table 12 Recovery From File Creation Failures (RDF Event 739) (continued) File System Error Recovery Action 60 through 66 Repair the device or clear the condition. 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. 130 through 139 Repair the device or clear the condition. 157 Check file integrity. 190 Repair the device or clear the condition. 199 Alter the security (probably Safeguard).
the updater associated with the volume may report RDF event 813 - "Concurrent file opens exceeds capacity". This happens if the updater has 3,000 files open and it must open a new file. Should this occur, the updater immediately generates the RDF event 813, commits its current transaction, closes all files, and restarts, which generates RDF event 837. When it restarts, it resumes processing image audit at the audit record for the file that caused the problem.
• Failure of a TMF audited volume on the primary system • TMF subsystem failure after which the TMF volume recovery is successful • TMF file recovery operation on the primary system that is not to a timestamp, first purge, or TOMATPOSITION position. • TMF ABORT TRANSACTION with the AVOIDHANGING option on the primary system RDF cannot recover from the following events: • TMF file recovery operation to a timestamp, first purge, or TOMATPOSITION on the primary system.
Processor Failures All RDF processes other than RDFCOM run as process pairs. If a CPU failure causes a primary RDF process to fail, the backup process takes over without interruption in service. If any RDF process pair stops unexpectedly, the monitor sends abort messages to the other RDF processes in order to bring about an orderly shutdown of RDF. You can then restart the subsystem by merely issuing a START RDF command.
Purger Failure If the primary CPU of the purger process fails, the purger process in the backup CPU takes over, the current PURGETIME interval is aborted, and a new PURGETIME interval is started. When the CPU that failed comes back up, RDF switches the purger to run on the reactivated primary CPU. If both the primary and backup CPUs of the purger process fail, RDF aborts. RDFNET Failure If the primary CPU of the RDFNET process fails, the RDFNET process in the backup CPU takes over.
Notice that these commands prevent any disk volumes on the local system from being enabled for TMF operations before starting the subsystem. 3. Reenable all pertinent disk volumes for TMF operations by entering the following command through TMFCOM: ~ENABLE DATAVOLS * When this command is executed, TMF performs its volume recovery operation on the audited volumes, and RDF reads the audit during this operation. 4.
The file recovery TOMATPOSITION is a special usage that achieves synchronization itself. If your RDF primary system has failed, you have executed an RDF takeover operation on your backup system without RDF/ZLT, and you have subsequently brought your primary system back online, you can resynchronize the database on your recovered primary system with file recovery TOMATPOSITION. When the takeover has completed on your backup system, RDF normally logs an RDF event 888.
TMFCOM ABORT TRANSACTION With AVOIDHANGING Option on Primary System Under some circumstances, the TMF Backout process on the primary system is not able to back out transactions from a data file (for example, hung transactions). If this situation arises, and if the file is protected by RDF, the user should avoid issuing the TMFCOM ABORT TRANSACTION command with the AVOIDHANGING option to abort such transactions.
There is a special circumstance that has caused trouble for some customers. Assume you are running RDF to protect your primary database. Now assume that someone configures a small RDF test subsystem, starts that test subsystem, stops it, and then deletes the RDF control subvolume on the primary and backup systems to eliminate all vestiges of that test subsystem.
1. TMF writes a shutdown record to the MAT. When the master extractor reads the shutdown record, it notifies the monitor that TMF has stopped. NOTE: If the extractor process falls way behind TMF because the communications lines to the backup system have been down and come up again, it can take some time for the extractor to get to the TMF shutdown record.
To stop the RDF and put the primary and backup databases into logically identical states (the data is the same although the physical structure of the files may differ between primary and backup), you must execute the following steps: • Issue a TMFCOM DISABLE BEGINTRANS command on the primary system. This command prevents the applications from initiating any new transactions until you issue a TMFCOM ENABLE BEGINTRANS command.
>RDFCOM DALLAS3; STOP RDF An alternative way to stop RDF on the backup system is to enter the following command through TACL: >STATUS *, PROG RDF-software-loc.*, STOP CAUTION: Issuing this command in this situation is only safe, however, if this is the backup system for a single RDF environment. Stopping RDF Using STOP RDF, DRAIN As stated above, stopping TMF shuts down RDF and it guarantees that the backup database is then logically identical to the primary database.
perform a planned switchover from the primary system to the backup system to keep applications running while you modify or repair the primary system. Below, the general steps involved in coordinating a switchover of business operations from the primary to backup system and back are provided. These only address the aspects of the switchover itself with regard to RDF operation and general business operations.
1. 2. 3. On the primary system, stop the applications that are updating your RDF-protected database. This is imperative. Watch for the extractor's RTD to be 0:00. Enter the STOP RDF, REVERSE command. When the extractor receives notice of the operation, it notes where it is in the audit trail and shuts down, and the updaters shut down as soon as they have reached the equivalent location. This is identical to the DRAIN command. Next, RDF automatically executes the REVERSE trigger that you have configured.
Please note that in each of these configurations, there is no possible overlap of data being replicated by the two RDF subsystems in a reciprocal configuration. See Reciprocal and Chain Replication in Chapter 1 for a discussion of the potential problem that can occur if you do not use one of the two methods described above. The steps for performing a planned switchover from \A to \B in such a configuration are: 1. On system \B, stop RDF subsystem # 2. Note the local system time; you will need it later. 2.
was stopped before it could send the final outcomes to the backup system. The takeover operation determines what audit needs to be backed out in order to bring the backup database into a stable and consistent state. Audit is backed out of the backup database during three possible undo passes, described below. With proper configuration of the RDF/ZLT product, no transactions that were committed on the primary system are ever lost due to an unplanned outage that requires an RDF takeover operation.
\London and the control subvolume was BOSTON, then you would enter the following RDFCOM command to the TACL prompt on \LONDON: > RDFCOM BOSTON The Takeover command has the ! option (see the syntax for this command in Chapter 8 ). If you do not include the ! sign, then RDFCOM tries to see if the monitor and extractor are still running on the primary system. If it can access the monitor or extractor because the primary system is still running, then RDFCOM aborts the command immediately.
3. To proceed with the takeover operation, enter Y or YES. To abort the takeover operation, enter N or NO. After you enter your response, RDFCOM returns its prompt. Once the Takeover operation is underway, you can use the STATUS RDF command to determine the progress of the takeover operation. If the takeover operation is still in progress, RDF displays the current state as “TAKEOVER IN PROGRESS.
When all of the updater processes have stopped, the purger logs either the RDF event number 724 or 725 before stopping. Event 724 indicates that the takeover completed successfully. Event 725 indicates that it did not, and you should reissue the TAKEOVER command. Event 724 is always followed by event 735, which indicates the last MAT position seen by the receiver process. The 735 event is used primarily for triple contingency. These events will be followed by either RDF event 888 or 858.
audit to be undone by an updater is large (for example, thousands of records), then logging an exception record for each record undone could slow down the takeover work of each updater. You can choose whether you want an exception record for each audit record undone during the takeover operation when you configure the RDF UPDATEREXCEPTION attribute. If you set it ON, the updater logs an exception record for each audit record on which it executes undo.
Therefore, taking an online dump before resuming business operations is important, but when do you do it? If you wait until after the RDF takeover operation has completed, then it could take many hours before the online dumps complete, and only then would it be safe to resume business operations. Thus, not taking regular online dumps of your backup database can lead to a significant length of time before you can safely resume business operations on your backup system.
c. d. If you use the same application for query processing as well as read/write access, and you are already performing query processing on your backup database, you will need to have the application close all files currently open for read-only access, and then reopen them for read/write access after the RDF takeover. In this sense, it may be advantageous to have one application that performs query processing and another that does read/write operations.
12. Test Your Switchover/Takeover Procedures You may not know whether you have everything you need on your backup system to move business operations from your primary system to your backup until you perform that task. If you wait until you actually encounter a disaster and must move business operations to the backup system, you may find that you are missing important items that you need.
Restoring the Primary System After you initiate a takeover, it is possible that the last committed transactions on the primary system did not make it to the backup system (meaning that the backup and primary databases are not synchronized). When the failed primary system is restored to operable condition you have two methods of resynchronizing your primary database with your backup database where your applications are now running. One method is online, and the other is offline.
8. 9. Turn on updating. When RDF has caught up, do a planned switchover from \B to \A (as described earlier). If you have an RDF Network, there are some situations where File Recovery with the TOMATPOSITION option is not possible. If that is the case, RDF logs an RDF Event 858 at the end of the takeover operation.
For a complete discussion of FASTUPDATEMODE, see the description for this attribute under the SET RECEIVER command in “Entering RDFCOM Commands” (page 176). While having FASTUPDATEMODE turned on does give you read access to data freshly committed on the primary system as soon as possible, please note that the option still only provides you with BROWSE access.
Because the updater may have applied some audit for transactions that had not yet committed at the specified timestamp, it then executes an undo pass to undo those specific records. For the undo pass, the purger builds an undo list based on those transactions that the updaters need to undo, the updaters read this list, and they read backwards in the image trail, performing logical undo operations on those records that need to be backed out.
The only operations that must be performed WITH SHARED ACCESS are merge partitions and move boundaries. It is recommended that you perform all other operations with nonshared access. NOTE: When you make DDL changes to your primary database, you can use the NonStop SQL DDL Replicator product to replicate NonStop SQL/MP DDL changes to your backup database automatically, instead of you having to perform those changes manually on the backup system.
to see all updaters have processed all image audit up to this special record. When the purger generates the RDF event 908, you are now ready to perform steps 2 and 3 above. CAUTION: While the NonStop SQL products allow a DDL change with Shared Access where the target is located on a different node, RDF does not support this. Consider an example where you gave a Table X on your RDF primary system \A and you want to create a new partition for the table on \B.
1. 2. 3. Execute a process that opens the image trail file with shared read access. This can be a simple process that you supply to perform only this operation. When the purger determines that all updaters are finished with this image trail file (named, say, AA000007), and have moved on to the next image trail file (named, say, AA000010), then it might try to purge AA000007. The purge operation will fail, however, because your process still has AA000007 open.
Of course, if you are taking online dumps of your backup database, you must also configure TMF to perform audit dumping either to tape or disk. Doing FUP RELOAD Operations With Updaters Running Because the backup database is audited by TMF, you cannot do FUP RELOAD operations on it unless you have altered the RDF UPDATEROPEN attribute to SHARED. Previously you needed to stop the updaters before you could alter this attribute, but RDF now allows you to do this online.
NOTE: If you enter the SCF PRIMARY DISK for an updater's UPDATEVOLUME, the affected updater might report a number of RDF 700 events with the file-system errors 10, 11, and 71. If these errors occur, they will be reported immediately following the disk primary event. In this situation, these errors can be expected and they do not indicate that the backup database has become inconsistent with the primary database.
6 Maintaining the Databases A vital task in working with RDF is to keep the backup and primary databases synchronized with each other.
Figure 8 Synchronized Databases During RDF Operations Figure 9 shows synchronized databases where the application is running on \PRIMARY and the transaction data for the three new transactions has been applied to the backup database. Figure 9 Synchronized Databases, No Outstanding Audit Figure 10 shows synchronized databases where TMF has just been shut down.
Figure 10 Synchronized Databases After STOP TMF Command Figure 11 shows unsynchronized databases. In this figure, T5 and T6 (transactions 5 and 6) have not been transmitted to the backup system because of a physical disaster, such as fire or flood, or because the primary or backup systems have failed.
NonStop SQL/MP or NonStop SQL/MX Databases For NonStop SQL/MP or NonStop SQL/MX databases, changes you need to perform manually on the backup system include: • Catalog changes • Results of DDL operations, including creating or altering tables and views • Partition key changes • Table purges Catalog Changes RDF regards NonStop SQL/MP and NonStop SQL/MX DDL operations like updates to SQL catalogs. Although SQL catalogs are audited tables, RDF does not replicate catalog changes.
(for example, double CPU failure), then it logs RDF event 905 that warns you that you need to restart updating. When restarted, the only updaters that do any work are those that terminated prematurely last time. When they reach the special record, they stop and the purger then logs the event 908. See the section “RDF and NonStop SQL DDL Operations” (page 142) for further discussion.
CATALOG \PRIM.$DATA.DBCAT; 2. Create an index based on first names in a database on the primary system. CREATE INDEX \PRIM.$DATA1.DB.FIRST ON \PRIM.$DATA1.DB.EMPLOYEE ( FIRST-NAME, LAST-NAME ), WITH SHARED ACCESS; 3. 4. Watch for the purger to log RDF event 908. On the backup system, set the default catalog for the backup database. CATALOG \BACK.$DATA.DBCAT; 5. Create the index for the backup database.
KEY ( COLUMN 0, OFFSET 0, LENGTH 4, ASC ) INDEX ( 1, $DATA.RDFSQL.MASTXYZ, <
To perform DDL operations on Enscribe files that RDF does not replicate, there are two methods to coordinate the operation: The STOP TMF Method 1. 2. 3. 4. 5. 6. Stop application processing on the primary system. Stop TMF on the primary system; wait for RDF to read the STOP TMF message in the audit trail and stop itself. Start TMF on the primary system so the operations on audited Enscribe files can be performed. Start RDF so that no audit trails are lost, but do not resume application processing.
NOTE: Resynchronization is not always necessary, however, after a file-system error in an RDF process. For example, an updater process reporting an error 122 will restart. • TMF is deleted and reconfigured, or RDF is reinitialized, after a STOP RDF command is issued at the primary system. If RDF fails and reports an event whose recovery text indicates that database resynchronization is required, you must resynchronize the backup and primary databases.
1. 2. 3. 4. 5. 6. Stop your applications. It is also recommended that you stop TMF too because this guarantees that no unexpected updates can touch the database, but it is not a requirement if you are certain you have stopped all update activity to the affected volume. Make a copy of the tables or files. Restart TMF on the primary system if you stopped it in Step 1. If you stopped TMF in Step 1, then wait for RDF to stop in response.
7 Online Database Synchronization With RDF/IMP, IMPX, or ZLT you can synchronize entire databases or selected volumes, files, tables or even partitions while your applications continue to run. For information about NonStop SQL/MX databases, see Chapter 16 (page 307). Overview The RDF online database synchronization protocol consists of the following general steps (the details of which are discussed later in this chapter): • Initialize the RDF configuration with the SYNCHDBTIME option.
NOTE: RDF does not replicate NonStop SQL/MP and NonStop SQL/MX catalogs. Therefore, if you are synchronizing NonStop SQL/MP and NonStop SQL/MX tables, you might need to create NonStop SQL/MP and NonStop SQL/MX catalogs manually on the backup system if they do not already exist. Synchronizing Entire Databases Online To synchronize an entire RDF backup database to the primary database online: 1. If RDF is currently running, issue a STOP RDF command on the primary system. 2.
6. If the duplicate tables and files were created on the primary system in step 4, use BACKUP/RESTORE or FUP DUP operations to copy them to the backup system. For ENSCRIBE files with alternate key files, after restoring the files to the backup system, if the name of the alternate key file is in network form, then you must manually alter the system name of the alternate key file in the file label, replacing the name of the primary system with that of the backup.
image trails. When synchronizing databases, you should configure image trail volumes that have a lot of free space for image files. The key problem you want to avoid is where your steps to obtain the copy and prepare it on the backup system take so long that your image trails run out of space before you are able to start the updaters.
If you did recently perform a NonStop SQL/MP or NonStop SQL/MXoperation with SHARED ACCESS on the primary system and you want to initialize the RDF subsystem to a synchdbtime, you must specify a synchdbtime such that the starting position in the MAT is after the Stop-RDF-Updater record. As a precaution, if RDFCOM encounters a Stop-RDF-Updater record during its backward search of the MAT, it issues a warning message to that effect asking if you want to proceed with initialization.
also create them on the backup system. You then must purge the files on your backup system before copying the loaded files from the primary system. General Considerations for NonStop SQL Tables • Key-sequenced tables without SYSKEY. To improve the performance of the load operations significantly, specify the SORTED option. • Tables with SYSKEY or Clustering Keys.
2. Start a new transaction, do a READUPDATELOCK on the record, and commit the transaction. This procedure pops the inserted record from the file, but leaves the special “dummy” record in the 0th position. You must do this operation before you start RDF updating. For information about the special “dummy” record in Enscribe Queue Files, see the information about queue files in the Enscribe Programmer’s Guide.
• If you use the SQLCI DUP or MXCI DUP command to move duplicate partitioned NonStop SQL tables, you must use the MAP NAMES option to specify the backup system name. • If you use the SQLCI DUP or MXCI DUP command to move NonStop SQL tables with index tables, you must use the MAP NAMES option to specify the backup system name. Example of Synchronizing An Entire Database Online Following is a summary of the steps necessary to perform an online synchronization of an entire database. 1.
After using a VOLUME command to specify the primary database volume from which you want to extract the data, load the empty duplicate files: 5. volume $data0.test load part0100, $data2.test.part0100, load part0101, $data2.test.part0101, load altf0100, $data2.test.altf0100, load altf0101, $data2.test.altf0101, share, share, share, share, sorted sorted sorted sorted volume $data1.test load part0200, $data3.test.part0200, load part0201, $data3.test.part0201, load altf0200, $data3.test.
You would start by synchronizing your first two volumes, following the guidelines for synchronizing an entire database. When this operation has completed and the RDF updaters are fully caught up, you stop the NonStop RDF product. You then delete your current RDF configuration and initialize a new RDF subsystem, using the SYNCHDBTIME option. For the timestamp to be used with the SYNCHDBTIME attribute, you specify a timestamp following the guidelines for the INITTIME option.
There are a variety of considerations when synchronizing portions of a database. Read the following carefully. Enscribe Files Without Partitions Key-Sequenced and Relative Files Use either Method 1 or Method 2 of Step 4 under “Synchronizing Entire Databases Online” (page 159) to obtain a new copy of the file-set. Then use BACKUP and RESTORE (or FUP DUP) to move the duplicate file to the backup system.
FUP CREATE $DATA1.TEMP.PART0100, LIKE $DATA1.TEST.PART0100, NO AUDIT That command creates the two files $DATA1.TEMP.PART0100 (primary partition) and $DATA2.TEMP.PART0100 (secondary partition) You must load all the partitions of a relative file. Therefore, only one command is possible. FUP LOAD $DATA1.TEST.PART0100, $DATA1.TEMP.PART0100, SHARE You can then use BACKUP and RESTORE (or FUP DUP) with the PARTONLY option to copy the loaded partition you need to the backup system.
Described below is a set of steps that can be used to synchronize individual partitions of NonStop SQL/MP tables (either primary or secondary partitions). NOTE: While the discussion below is concerned with NonStop SQL/MP, the same issues and resolutions apply for NonStop SQL/MX. Requirements for Synchronization of Individual Partitions To synchronize an individual partition of a partitioned table, you must have a copy of the entire table on the backup system.
For the timestamp, follow the guidelines for the INITTIME option. 3. 4. Configure RDF and then issue a START RDF, UPDATE OFF command on the primary system. Make a copy of your table using one of the following two methods: • Method 1 Create the entire duplicate table on your backup system with a temporary name at a temporary location (such as \BACKUP.$DATA.DUP.PART). The alternative is to create the duplicate table on the primary system at a temporary location (such as \PRIMARY.$DATA.DUP.PART).
15. When the extractor has logged the message indicating it has completed its role in the online synchronization operation, issue the RDFCOM START UPDATE command on your primary system. The preceding procedure preserves indexes you might have on the backup system. There is an alternate method that might be faster in some situations than the method described above, although this method requires that you rebuild all indexes associated with the table on the backup system. 1.
8. If you created the duplicate table on the primary system, then use the RESTORE utility to put the entire duplicate table with all its partitions onto disk on the backup system. You must use MAP NAMES to correct the system name. $DATA.DUP.PART is now on the backup system. If you created the duplicate table directly on the backup system, skip this step. 9. 10. 11. 12. 13. 14. 15. 16.
Phase 1, Part 2 The extractor has reached the next TMP control point record in the audit trail and now has a list of all transactions that might have been started during the create/load or backup operation. The extractor generates a synch-phase-1-complete record, and then continues its normal operation. Upon completion of phase 1, part 2, the extractor logs message 767.
the extractor can log messages 766, 767, and 768 again, even if it had logged any of them prior to the restart condition. Determining When Online Database Synchronization Is Complete The following RDF messages assist you in knowing when the various phases of online database synchronization are complete: Extractor Messages Messages 766, 767, and 768 in combination report the completion of phase 1. Message 782 reports the completion of phase 2.
8 Entering RDFCOM Commands To manage, operate, and control RDF and its environment, you enter commands through the RDFCOM online utility. This chapter, directed to system managers and operators, describes the RDFCOM commands and their attributes.
command, the default security requirements appear under the heading “Security Restrictions.” In general, the default security restrictions for RDFCOM commands are: • The EXIT, FC, HELP, HISTORY, INFO, OBEY, OPEN, OUT, SHOW, and STATUS commands can be used by all users. • The START RDF and TAKEOVER commands can only be used by the member of the super ID group who initialized RDF. • The other RDFCOM commands can be used only by members of the super ID group.
Table 13 Systems for RDFCOM Commands (continued) Extractor Image Monitor RDF Receiver Purger Trail Update Volume RDFNET Network Trigger SET P P P P P P P P P P SHOW P E E E E E E E E E E E START STATUS P E E STOP Other Objects P E E E E** P P* TAKEOVER B UNPINAUDIT P VALIDATE P Legend P = Primary only B = Backup only E = Either * = SYNCH ** = RTDWARNING Table 14 Default User Security for RDFCOM Commands Extractor Image Monitor RDF Receiver Purger Trail ADD S ALT
Table 14 Default User Security for RDFCOM Commands (continued) Extractor Image Monitor RDF Receiver Purger Trail INFO A A A INITIALIZE A A Update Volume RDFNET Network Trigger A A A A A Other Objects A* O* OBEY X OPEN A OUT A RESET S S S S S S S S S S SET S S S S S S S S S S SHOW A A A A A A A A A A A* A A START STATUS STOP O* A A* S* S* A* A* S* A** S*** TAKEOVER O UNPINAUDIT S VALIDATE S Legend: A = All users S = Super-user group only O
These names typically identify objects such as disk files, log devices, and processes. Errors can result from improperly specifying these names in RDFCOM commands. In almost all commands, these names are governed by the common syntax rules described in the following paragraphs. Where exceptions to these rules occur, they are noted in the individual command descriptions. The system does not distinguish between uppercase and lowercase alphabetic characters in a file name.
system specifies the name of the system on which the device resides. A system name consists of a backslash (\) followed by one to seven alphanumeric characters; the first alphanumeric character must be a letter. device-name specifies the name of a device. A device name consists of a dollar sign ($) followed by one to seven alphanumeric characters; the first alphanumeric character must be a letter. qualifier is an optional qualifier.
ADD The ADD command applies configuration parameter values for the specified process or other object from the RDF configuration memory table to the RDF configuration file. ADD {RDF {MONITOR {EXTRACTOR {RECEIVER {IMAGETRAIL $volume {PURGER {RDFNET {NETWORK {[VOLUME] $volume {TRIGGER trigger-type } } } } } } } } } } RDF applies RDF global configuration parameters. MONITOR applies configuration parameters for the monitor. EXTRACTOR applies configuration parameters for an extractor.
Usage Guidelines With the ADD command, all configuration parameter settings that you previously supplied in SET commands for the particular process or other object are applied from the RDF memory table to the RDF configuration file. Any parameter settings that you did not supply are set to their default values. Each volume on the primary system protected by RDF requires a corresponding updater process on the backup system.
When the preceding command sequence is executed, all of the other RDF global parameters are set to their default values: (In this list, \LONDON is the system at which you issued the command sequence.
trigger-type is REVERSE or TAKEOVER. This command parameter alters a trigger that has already been added to the RDF configuration. Where Issued These commands can be issued only at the primary system, except altering the TAKEOVER trigger, which can also be issued on the backup system if and only if the primary system is not available. NOTE: You should only alter the TAKEOVER trigger on the backup system if you are about to issue the TAKEOVER command.
To change the primary and backup CPUs for the master receiver process to CPUs 3 and 4 respectively, enter an ALTER RECEIVER CPUS command: ]ALTER RECEIVER CPUS 3:4 Remember you cannot do this particular alter operation while RDF is running. To change the primary and alternate CPUs of a reverse trigger to CPUs 3 and 4, enter an ALTER TRIGGER CPU command: ]ALTER TRIGGER REVERSE CPUS 3:4 COPYAUDIT This command is only for use with the triple contingency feature.
\A ------------------> \C (The RDF control subvolume is A2 on both systems.) Assume you have lost the original primary system (\A), you have successfully completed a takeover on both backup systems (\B and \C), and the MAT positions displayed by the respective 735 messages are: \B: \C: 735 LAST MAT POSITION: Sno 10, RBA 100500000 735 LAST MAT POSITION: Sno 10, RBA 100000000 500 kilobytes of audit records is missing at \C.
If RDFCOM encounters network problems during any other phase of COPYAUDIT execution, it does not abend. Instead, it logs a message to the home terminal and aborts the COPYAUDIT command. Example Assume you have established two RDF configurations to provide triple contingency protection (\A to \B and \A to \C) and that the RDF control subvolume of the \A to \B configuration is A1 and the RDF control subvolume of the \A to \C configuration is A2.
Usage Guidelines For the DELETE command to have any effect, a configuration record must already exist for the secondary image trail or updater process associated with the volume name supplied (that is, someone must have previously issued an ADD IMAGETRAIL or ADD VOLUME command for the volume). When you issue a DELETE VOLUME command, RDF responds: • The extractor process stops sending image data for the volume specified in the DELETE VOLUME command.
Security Restrictions None; anyone can enter the EXIT command. RDF State Requirement You can issue the EXIT command at any time, whether or not RDF has been started. Usage Guidelines If you issue the EXIT command in your current RDFCOM session, RDFCOM terminates the session and returns control to the operating system. If the EXIT command appears in a command file, RDFCOM stops reading the command file and ignores any commands in the file that follow the EXIT command.
RDF State Requirement You can enter the FC command at any time, whether or not RDF has been started. Usage Guidelines When you issue an FC command, the requested command appears, followed by a subcommand prompt (.). At the prompt, you can enter the subcommands R, I, or D to respectively replace, insert, or delete characters in the command line. As a simpler alternative to the R subcommand, you can simply enter the replacement character directly under the character you want to replace.
. RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF SOFTWARELOC LOGFILE PRIMARYSYSTEM UPDATERDELAY UPDATERTXTIME UPDATERRTDWARNING UPDATEROPEN NETWORK NETWORKMASTER UPDATEREXCEPTION REPLICATEPURGE OWNER $SYSTEM.RDF $0 \MICKEY 10 60 60 PROTECTED OFF OFF ON OFF SUPER.RDF HELP The HELP command displays explanatory text about RDFCOM commands and RDF messages. HELP [ABBREVIATIONS ] [ALL ] ] [command [RDF-msg-number] ABBREVIATIONS lists the allowed abbreviations for RDFCOM command keywords.
{ TRIGGER { VOLUME $volume { $volume Cannot be performed with RDF } } } running. Only a user in the SUPER group can execute this command.
operator inadvertently issuing a STOP command from TACL. Effect: The backup process takes over, but not in fault-tolerant mode, until the primary process can be re-created. Recovery: This is an informational message; no recovery is required. HISTORY The HISTORY command displays the ten most recently issued RDFCOM commands (including the HISTORY command itself). HISTORY Where Issued Primary or backup system. Security Restrictions None; anyone can enter the HISTORY command.
{RDF {MONITOR {EXTRACTOR {RECEIVER {RDFNET {NETWORK {PURGER {TRIGGER trigger-type {VOLUME * {[VOLUME] $volume } } } } } } } } } } * displays the current configuration parameter values for the RDF global options, for all updater volumes, and for all RDF processes. [ATINDEX audittrail-index-num] is an integer value from 0 through 15 identifying the TMF audit trail on the primary system with which the particular RDF object is associated. 0 specifies the MAT.
RDFNET displays the current configuration parameter values for the RDFNET process. NETWORK displays the current configuration parameter values for an RDF network. PURGER displays the current configuration parameter values for the purger process. TRIGGER trigger-type displays the current configuration parameter values for the specified trigger type (REVERSE, TAKEOVER, or * ). INFO TRIGGER * displays both REVERSE and TAKEOVER triggers, if any are defined.
RDF RDF RDF RDF RDF UPDATEROPEN PROTECTED NETWORK OFF NETWORKMASTER OFF UPDATEREXCEPTION OFF REPLICATEPURGE OFF MONITOR CPUS 1:2 MONITOR PRIORITY 165 MONITOR PROCESS $MON1 EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR PURGER PURGER PURGER PURGER PURGER ATINDEX 0 CPUS 2:1 PRIORITY 165 PROCESS $EXT RTDWARNING 60 CPUS 3:2 PRIORITY 165 PROCESS $PURG RETAINCOUNT 50 PURGETIME 60 RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER ATINDEX 0 CPUS 1:2 EXTENTS (1000,1000) PRIORITY 165 RDFVOLUME $
TRIGGER PRIORITY 150 TRIGGER NOWAIT TRIGGER REVERSE The primary system name is set implicitly and the backup system name is set in the INITIALIZE RDF command.
RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF UPDATERDELAY 10 UPDATERTXTIME 60 UPDATERRTDWARNING 60 UPDATEROPEN PROTECTED NETWORK OFF NETWORKMASTER OFF UPDATEREXCEPTION ON REPLICATEPURGE OFF REMOTE MIRROR OFF RDF/IMPX/ZLT The primary system name is set implicitly and the backup system name is set in the INITIALIZE RDF command.
VOLUME PRIORITY 160 VOLUME PROCESS $UP03 VOLUME UPDATEVOLUME $DATA3 INFO PURGER Command To display the current configuration parameters for the purger process, enter the following command: ]INFO PURGER The output shows that the purger is configured with the following parameter values: running in CPUs 3 and 2, with a priority of 165, a retaincount of 50, a purgetime of 60, and the process name $PURG: PURGER PURGER PURGER PURGER PURGER CPUS 3:2 PRIORITY 165 PROCESS $PURG RETAINCOUNT 50 PURGETIME 60 INFO T
INFO NETWORK Command To display the current RDF network configuration parameters, enter the following command: ]INFO NETWORK RDF displays the following: NETWORK NETWORK NETWORK NETWORK PRIMARYSYSTEM \RDF04 BACKUPSYSTEM \RDF06 RCSV RDF04 PNETTXVOLUME $DATA07 INITIALIZE RDF The INITIALIZE RDF command creates the RDF configuration and context files for establishment of a new RDF configuration.
hour is a number from 0 to 23. min is a number from 00 to 59. min must be preceded by a colon (:). INITTIME : | NOW is a timestamp used for online product initialization. It has the same format as the timestamp parameter described above. NOW causes RDF to be initialized at the current date and time. To determine the appropriate value to use as the inittime parameter, first issue an RDFCOM STATUS RDF command and take note of the highest updater RTD time.
• If you include the INITTIME option without the ! option, RDFCOM displays: Do you wish to proceed? [Y/N] Enter Y or YES to proceed; enter N or NO to cancel the command. If you enter Y or YES, RDFCOM displays: Please wait while RDF searches for the specified timestamp. Initialization point for 12JAN2004 14:30 has been found. RDF will start at RBA: 376275 MAT file: $AUDIT.ZTMFAT.AA000414 Do you still wish to start at this point? [Y/N] Enter Y or YES to proceed; enter N or NO to cancel the command.
TMF must be started on the primary system, but transaction processing need not be enabled, when you enter the INITIALIZE RDF command either with or without the TIMESTAMP, INITTIME, or SYNCHDBTIME options. The INITIALIZE RDF command creates the configuration and context files for establishment of a new RDF configuration. After issuing the INITIALIZE RDF command, you must build the new configuration by entering the appropriate SET and ADD commands or by executing a command file containing those commands.
• If you plan to include the TIMESTAMP option in the INITIALIZE RDF command, make sure that the primary system database is backed up after the TMF shutdown so that the backup database can be restored at this point in the audit trail. Consider the following example: 1. TMF and RDF subsystems are running. 2. TMF subsystem is stopped, and RDF subsystem subsequently stops. 3. TMF subsystem is started and application processing resumed. 4. TMF subsystem is stopped.
OBEY The OBEY command executes a series of commands entered in a command file. OBEY [\system.][$volume.][subvolume.]file system identifies the system on which the command file is stored. volume identifies the disk volume on which the command file is stored. subvolume identifies the subvolume on which the command file is stored. file identifies the command file, which contains one or more valid RDFCOM commands. Where Issued Primary or backup system.
control-subvol is the name of the RDF control subvolume on both primary and backup systems. The control subvolume name is comprised of the primary system name of the RDF configuration (without the backslash) plus the optional character suffix if you included one in the INITIALIZE RDF command. Where Issued Primary or backup system. Security Restrictions None; anyone can enter the OPEN command. RDF State Requirement Before you can enter the OPEN command, RDF must have been initialized.
]INFO * In the two OPEN commands above, you do not include a backslash (\) because you are specifying the RDF control subvolume name (not a system name). OUT The OUT command redirects the output of the current RDFCOM session to the specified device or file. OUT [\system.][$volume.][subvolume.][file] system identifies the system on which the output file is stored. volume identifies the disk volume on which the output file is stored. subvolume identifies the subvolume on which the output file is stored.
The next OUT command establishes the destination of the text produced by the OBEYFORM option in the subsequent INFO RDF command as a command file named CONFY. The second OUT command in this sequence redirects later output back to your terminal: ]OUT CONFY ]INFO RDF, OBEYFORM ]OUT RESET The RESET command resets all configuration parameters for the specified entity to their default values within the RDF configuration memory table.
Security Restrictions You can issue the RESET command if you are a member of the super ID group. RDF State Requirement You can enter the RESET command at any time, whether or not RDF has been started. Certain constraints, however, apply to the subsequent ADD commands that apply the RESET values to the configuration file. For further information, see the ADD command description.
PROCESS process-name identifies the process name for the extractor process; process-name is any unique, valid process name of up to six characters; the first character must be a dollar sign ($). You cannot specify any of the reserved process names listed in the Guardian Procedure Calls Reference Manual. This parameter is not optional. You must explicitly name the extractor process.
Furthermore, RDF objects with a particular ATINDEX value greater than 0 must together constitute a complete set: • If there is an extractor with an ATINDEX value of 1, there must also be a receiver with an ATINDEX value of 1. • If there is a receiver with an ATINDEX value of 1, there must also be a secondary image trail with an ATINDEX of 1.
Usage Guidelines For ATINDEX values greater than 0, the specified value must match the audit trail number of a configured auxiliary audit trail. If you specify SET IMAGETRAIL ATINDEX 2, for example, there must be a configured auxiliary audit trail AUX02. Furthermore, RDF objects with a particular ATINDEX value greater than 0 must together constitute a complete set: • If there is an extractor with an ATINDEX value of 1, there must also be a receiver with an ATINDEX value of 1.
values do not affect the subsystem until they are applied to the RDF configuration file with the ADD command. Example To configure a monitor process named $MON1 to run in CPUs 0 and 1 at a priority of 180, issue the following commands after RDF has been initialized: ]SET ]SET ]SET ]ADD MONITOR PROCESS $MON1 MONITOR CPUS 0:1 MONITOR PRIORITY 180 MONITOR SET NETWORK The SET NETWORK command sets RDF network configuration parameters within the RDF configuration memory table.
Example To configure the primary system \RDF04 and backup system \RDF06, issue the following commands after RDF has been initialized: SET SET SET SET ADD NETWORK NETWORK NETWORK NETWORK NETWORK PRIMARYSYSTEM \RDF04 BACKUPSYSTEM \RDF06 REMOTECONTROLSUBVOLUME RDF04 PNETTXVOLUME $DATA07 SET PURGER The SET PURGER command sets purger process configuration parameters within the RDF configuration memory table.
Suppose that the image trail files are relatively small, such that the audit record at MAT 10, 100000010 was placed at the start of image trail file AA000025 on \B. If the purger on \B is allowed to purge AA000025 before the takeovers occur, the triple contingency protocol will fail because \C is missing some of the purged audit records (Sno 10, RBA 100000010 through Sno 10, RBA 100500000).
]SET ]SET ]SET ]ADD PURGER PROCESS $PRG PURGER CPUS 0:1 PURGER RETAINCOUNT 8 PURGER By default, in this example the purger process will run at a priority of 165 and the purger purgetime is set to 60 minutes. SET RDF The SET RDF command sets RDF global configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD RDF command.
In RDF environments with low to moderate updater activity and where no other transaction activity is occurring on the backup system, you could raise the tx-time without affecting TMF performance on the backup system. UPDATERRTDWARNING rtd-time specifies the RTD warning threshold (in seconds, 0 or greater) for all configured updaters. The default is 60 seconds. This threshold is used by the STATUS RTDWARNING command to determine which updaters, if any, are to be included in its display.
to the Master Audit Trail (MAT), and either the entire volume or at least the lockstep file must be protected by the RDF subsystem. For information about the RDF lockstep capability, see Chapter 15 (page 292). REPLICATEPURGE {ON | OFF} specifies whether Enscribe purge operations on the primary system are to be replicated on the backup system. When set to OFF (the default value), Enscribe purge operations are not replicated.
Security Restrictions None. RDF State Requirements None. Usage Guidelines The SET RDF command enters the global parameter values specified in this command into the RDF configuration table in memory. This table serves as an input buffer only, and so these values do not affect the subsystem until they are applied to the RDF configuration file with the ADD command. SET RDFNET The SET RDFNET command sets RDFNET process configuration parameters within the RDF configuration memory table.
Example To configure a RDFNET process named $MNET to run in CPUs 0 and 1 at a priority of 180, issue these commands after RDF has been initialized: ]SET ]SET ]SET ]ADD RDFNET PROCESS $MNET RDFNET CPUS 0:1 RDFNET PRIORITY 180 NETRDF SET RECEIVER The SET RECEIVER command sets receiver process configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD RECEIVER command.
PROCESS process-name specifies the process name for the receiver process; process-name is any unique, valid process name of up to six characters; the first character must be a dollar sign ($). You cannot specify any of the reserved process names listed in the Guardian Procedure Calls Reference Manual. Names longer than six characters, including the $ sign, are invalid. This parameter is not optional. You must explicitly name the receiver process.
Furthermore, RDF objects with a particular ATINDEX value greater than 0 must together constitute a complete set: • If there is an extractor with an ATINDEX value of 1, there must also be a receiver with an ATINDEX value of 1. • If there is a receiver with an ATINDEX value of 1, there must also be a secondary image trail with an ATINDEX of 1.
infile is the name of an edit file that will be passed as the IN file to the trigger process when it is created. infile must be a properly-formed Guardian disk file name. The file does not have to exist. This parameter is mandatory. outfile is the name of a file or process that will be passed as the OUT file to the trigger process when it is created. outfile must be a properly-formed Guardian disk file or process name.
The RDF configuration on \RIGHT is contained in the file \RIGHT.$DATA01.RDFCONF. RIGHT (specified in the INFILE). That file includes these commands (the standard SET/ADD RDF, EXTRACTOR, RECEIVER, PURGER, IMAGETRAIL and VOLUME configuration commands are omitted): INITIALIZE RDF, BACKUPSYSTEM \LEFT, INITTIME NOW ! START RDF Initially, RDF runs from \LEFT to \RIGHT.
IMAGEVOLUME $volume identifies a disk volume associated with a secondary image trail previously added to the RDF configuration (by way of an ADD IMAGETRAIL command), implicitly associating this updater process with that trail. This parameter is required. There is no default. An updater must always be explicitly associated with a secondary image trail. UPDATEVOLUME $volume specifies what volume on the backup system will receive database updates for the corresponding volume on the primary system.
Furthermore, RDF objects with a particular ATINDEX value greater than 0 must together constitute a complete set: • If there is an extractor with an ATINDEX value of 1, there must also be a receiver with an ATINDEX value of 1. • If there is a receiver with an ATINDEX value of 1, there must also be a secondary image trail with an ATINDEX of 1.
]SET ]SET ]SET ]ADD VOLUME VOLUME VOLUME VOLUME UPDATEVOLUME $DATA2 INCLUDE OEM2*.* INCLUDE OEM5*.* $DATA02 SHOW The SHOW command displays the current parameter values contained in the RDF configuration memory table for the specified process. With this command, you can confirm the parameter values before issuing the ADD command that actually applies them to the configuration file.
Usage Guidelines This command retrieves information from the RDF configuration memory table, which serves as an input buffer for a subsequent ADD command. If you have not yet issued any SET commands for the specified object, or have issued a RESET command for it, the SHOW command displays the default option values for the object. If you want to see what parameter values are already set in the configuration file, use the INFO command.
RDFCOM includes the line containing PROCESS process-name in the display only if the process name was specified in a SET command. SHOW PURGER Command Suppose that a series of SET PURGER commands specifies that a purger process named $PURG is to run in CPUs 3 and 2 at priority 165 with a RETAINCOUNT of 50.
SHOW NETWORK Command Suppose that a series of SET NETWORK commands specifies \RDF04 as the network master’s primary system, \RDF06 as the network master’s backup system, RDF04 as the network master’s remote control subvolume, and $DATA07 as the network master’s PNETTXVOLUME volume.
If you have initialized the TMF and RDF subsystems before issuing the START RDF command, RDF automatically begins transmitting audit data from the beginning of the first audit-trail file. CAUTION: If you initialize RDF after a STOP RDF command is issued at the primary system, you might need to resynchronize the databases before restarting RDF. TMF must be started and transactions enabled on both primary and backup systems before you issue the START RDF command.
Example To initiate updating on the backup system of all volumes protected by RDF, enter: ]START UPDATE STATUS The STATUS command displays current configuration information and operational statistics for the RDF environment, or specified portions thereof. All forms of the STATUS command, except STATUS RTDWARNING, automatically include information and statistics for the monitor process.
Security Restrictions None; anyone can enter a STATUS command. RDF State Requirement You can enter a STATUS command at any time after RDF has been initialized. Usage Guidelines The STATUS command provides you with the most current information about RDF and its operational status, presenting data for the specified RDF processes. STATUS RDF Command Output Display The output of the STATUS RDF command shows all critical information about each configured RDF entity.
represents all possible RDF states. For a discussion of each of these states, see “Displaying Current Operating Statistics and Configuration Information” (page 104) in Chapter 4.
Name The second column specifies the name of each process. Because the secondary image trails $IMAGE0 and $IMAGEA1 are not processes, they do not have process names or RTD times. In the second example above, observe that the monitor no longer has the configured process name. The reason for this is that the monitor started on the backup system for a takeover operation is started with a Guardian-generated name.
Volume and Seqnce The fifth and sixth columns together specify a file associated with each process: • The monitor entry reflects the name of the latest MAT file to which TMF is writing ($AUDMAT.ZTMFAT.AA000056 in this example). • Each extractor entry reflects the name of the TMF audit trail file from which it is reading ($AUDMAT.ZTMFAT.AA000056 for the master extractor and $AUDAUX1.ZTMFAT.BB000004 for the auxiliary extractor in this example).
database is no longer in synchronization with the primary system's database. If you stop RDF and then restart it, any asterisks previously reported are cleared until a process encounters a new unexpected error condition. sync During an online database synchronization operation, an updater reports "sync" in this column until it has caught up and has gone past the point when the STOP SYNCH command was issued.
STOP RDF The STOP RDF command shuts down RDF. STOP RDF { [, DRAIN ] } { [, REVERSE ] } DRAIN causes the following actions: • All TMF audit records up to the time the command is entered are stored in the image trails on the backup node. • The RDF processes shut down in a manner similar to when a stop TMF record is encountered in the audit trail. • Each updater shuts down after it has applied all audit records up to the stop point.
lines are up. In addition to stopping TMF, this action stops all RDF processes and saves the context of each process in a file. Alternatively, if you have multiple applications running on your primary system and not all of the databases are RDF-protected, then stopping TMF to coordinate a planned and synchronized shutdown may not be possible.
The STOP RDF, REVERSE command is a special purpose function designed for a fast switchover operation. See the related discussion in “Critical Operations, Special Situations, and Error Conditions” (page 113). RDF must be running in the Normal state (with Update On) to issue a STOP RDF, DRAIN or STOP RDF, REVERSE command.
If you use the TIMESTAMP option, the operation is called a stop-update-to-time operation, which is discussed further below. NOTE: The timestamp you specify must be at least 5 minutes later than the current time at your primary system. If you specify an earlier time, an error message appears. Additionally, all transactions that committed prior to the timestamp are applied and retained in the backup database.
Stable Access” (page 141) in Chapter 5. A stop-update-to-time operation typically includes an undo pass to back out any updates the updaters may have applied for transactions that did not commit by the specified timestamp. Any transactions backed out are reapplied when you issue the next START UPDATE command. If you issue the STOP UPDATE command without the TIMESTAMP option, the RDFCOM prompt is not returned until all updaters have stopped.
Usage Guidelines The TAKEOVER command is customarily issued when the primary system fails or otherwise becomes unavailable, and you want to make the backup database your new database of record for your applications. CAUTION: The TAKEOVER command is not a normal operational command. Operators should never issue this command strictly on their own initiative. Issue this command only when specifically told to do so by someone in high authority.
updaters; if UPDATEREXCEPTION is ON, then each update of the batch needs to be undone and an exception record written. • Auxiliary Audit and a Comm Problem If your RDF environment includes extractor-receiver pairs associated with auxiliary audit trails, then if one extractor-receiver pair has fallen way behind because of a communications problems, then all affected transactions must be undone by all affected updaters, and this can lead to a lot of audit being undone with exception records.
After you enter your response, RDFCOM prompts you for your next command. 4. Having initiated the RDF TAKEOVER operation, you can then use a STATUS RDF command to determine the status of the TAKEOVER operation. If the TAKEOVER operation is still in progress when you enter the STATUS RDF command, the subsystem displays the current state as “TAKEOVER IN PROGRESS.
VALIDATE CONFIGURATION The VALIDATE CONFIGURATION command validates the parameters in the RDF configuration file and optionally generates a report on the status of validations. VALIDATE CONFIGURATION [, REPORT [filename]] where, REPORT [filename] is an optional parameter used to generate report on the result of validations. Validation reports for the following scenarios are generated: • A filename is not provided, the report is generated on the screen.
• The volumes for the image files (specified by the RDFVOLUME option of a SET RECEIVER command and any ADD IMAGETRAIL commands) are valid and exist on the backup system. • The volumes for the image files have enough room for two more image files (for an RDF restart). • The primary volumes associated with the updater processes are valid and are being audited to the TMF audit trail.
Receiver Purger Updater Updater CPU UP Check.......................Both CPUs Up - N:$MRCV PF:\TESTSYS2.$SYSTEM.BKPRDF.RDFRCVO Program File License Check.........Passed CPU UP Check.......................Both CPUs Up - N:$MR04 PF:\TESTSYS2.$SYSTEM.BKPRDF.RDFPRGO Program File License Check.........Passed CPU UP Check.......................Both CPUs Up - N:$MR10 PF:\TESTSYS2.$SYSTEM.BKPRDF.RDFUPDO Program File License Check.........Passed CPU UP Check.......................
9 Entering RDFSCAN Commands All RDF messages are directed to an EMS event log (collector). To examine that log without looking at all events for the entire system, you first use the standard EMS filter RDFFLTO to create an intermediate entry-sequenced file copy of the RDF log, and then enter commands through the RDFSCAN online utility. This chapter, which is written for system managers and operators, describes the RDFSCAN commands and their attributes.
In addition, this element is included only if applicable: • Output Displayed: Only two RDFSCAN commands (LIST and SCAN) produce output, although others influence its content and destination. For information about the other elements, see “Command Description Elements” in Chapter 8 (page 176). Except for the LOG and NOLOG commands, you can abbreviate the command name by entering only the first character (such as L for LIST) or any number of the leading characters (such as DIS for DISPLAY).
OFF disables the display of record numbers. Usage Guidelines The DISPLAY function is automatically enabled if pattern matching is enabled and is automatically disabled if pattern matching is disabled. For information about enabling and disabling pattern matching, see the MATCH command description in “MATCH” (page 256). Examples Suppose that $SYSTEM.SANFRAN.
Examples If you issue an EXIT command in response to the RDFSCAN prompt, RDFSCAN terminates the session and displays a logoff message: Enter the next RDFscan function you want: Thank you for using RDFscan EXIT If you press Ctrl-Y in response to the RDFSCAN prompt, RDFSCAN terminates the session and displays an end-of-file indication followed by the logoff message: Enter the next RDFscan function you want: EOF! Ctrl-Y Thank you for using RDFscan FILE The FILE command selects a file generated by the RDFF
HELP The HELP command displays the syntax of RDFSCAN commands or introductory information about the RDFSCAN utility. HELP [ ALL ] [ INTRO ] [ command ] ALL displays the syntax of all RDFSCAN commands. INTRO displays information on how to use the RDFSCAN utility. command displays the syntax of the RDFSCAN command indicated by command.
If pattern matching is disabled, the LIST command displays the specified number of messages starting at the current record. This behavior is identical to using the SCAN command with pattern matching disabled. For information about enabling and disabling pattern matching, see the MATCH command description in “MATCH” (page 256).
Usage Guidelines The LIST command always transmits its output to the standard output device for RDFSCAN, which is normally your terminal. When you specify a destination file in the LOG command, RDFSCAN directs subsequent LIST command output to that destination file as well as producing it on the standard output device. That is, with the LOG command, LIST output goes both to your terminal and the file specified in LOG.
To disable pattern matching, merely press the RETURN key at the prompt without entering a pattern. When entering a match pattern, you can use asterisks (*) and question marks (?) as wild-card characters. When pattern matching is enabled, the DISPLAY function is automatically enabled; when pattern matching is disabled, the DISPLAY function is automatically disabled. Table 15 shows the symbols RDFSCAN uses in pattern matching.
Examples This command disables the copying of LIST command output: Enter the next RDFSCAN function you want: NOLOG File: $SYSTEM.SANFRAN.RDFLOG, current record: 9454, last record: 9466 Enter the next RDFSCAN function you want: SCAN The SCAN command scans a specific number of messages in the file and displays all of those in that range that contain the current match pattern. SCAN number number is the number of messages to scan within the log file.
Record number: 1011 2004/06/08 04:13:49 \LAB1 $AU02 790 Backup Process Created in Processor 03 Record number: 1342 2004/06/08 04:13:49 \LAB1 $AU02 718 Switched to original Primary Processor Record number: 1792 2004/06/08 05:01:35 \LAB1 $AU02 790 Backup Process Created in Processor 03 Record number: 1933 2004/06/08 05:01:35 \LAB1 $AU02 718 Switched to original Primary Processor File: $SYSTEM.SANFRAN.
10 Triple Contingency The triple contingency feature makes it possible for your applications to resume running with full RDF protection within minutes after loss of your primary system. NOTE: Replication of network transactions is not supported in conjunction with the triple contingency feature, nor is the replication of auxiliary audit trails.
(that is, which system had received the least amount of audit data from the extractor by the time the primary system was lost). • On the backup system that was further behind (had the least amount of audit data), issue the COPYAUDIT command specifying the name of the other backup system and its RDF control subvolume. That command copies over all missing audit records from the designated system. • Upon successful completion of the COPYAUDIT operation, do a second takeover on that system.
The RETAINCOUNT Configuration Parameter The purger RETAINCOUNT parameter specifies how many image trail files (including the one currently in use) must be retained on disk for each image trail. The default value for this parameter is two. This parameter is important because if you lose the primary system, the triple contingency protocol will work only if one of the backup systems has retained all of the audit records that the other is missing.
where num is once again within the range 2 through 5000. (Before entering this command, however, you must first stop RDF.) The COPYAUDIT Command If the primary system fails, you must execute two takeovers: one on each backup system.
If the takeover completes successfully (the receiver logs an RDF message 724 followed by a 735 message containing the same detail as in the 735 message associated with the takeover on \B), the two databases are logically identical. At that point you can initialize, configure, and start RDF on both systems and then resume application processing on the new primary system with full RDF protection. COPYAUDIT Restartability The COPYAUDIT command is restartable.
When the takeover operations are complete, the databases on systems \B and \C are logically identical to one another, you have not lost any committed data regardless of the number of auxiliary audit trails involved. Figure 12 RDFZLT with Triple Contingency Summary To be able to use the triple contingency feature, you must: 1. Establish two RDF configurations with the same primary system and separate backup systems. 2.
11 Subvolume-Level and File-Level Replication By default, RDF provides volume-level protection, wherein changes to all audited files and tables on each protected primary system data volume are replicated to an associated backup system data volume. RDF/IMP, IMPX, and ZLT also support subvolume-level and file-level replication. To use this capability, you supply INCLUDE and EXCLUDE clauses when configuring updaters to identify specific subvolumes and files you want either replicated or not replicated.
Wildcard Character (*) The asterisk (*) can be used as a wildcard character in both subvolume and file names. Within Subvolume Names When used to designate subvolume names, the * must always be used as a suffix. su*v.fname, *.fname, and *.*, for example, are not valid. But DB*.filename is valid because the asterisk is used as a subvolume name suffix. In this case, changes made to all audited files and tables on all subvolumes whose name starts with DB on the protected data volume are replicated.
SET SET SET SET SET SET SET SET ADD VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME CPUS 1:2 IMAGEVOLUME $IMAGE PRIORITY 185 PROCESS $MM02 UPDATEVOLUME $DATA02 INCLUDE SBSUBVOL.MYFILE INCLUDE SBTEST10.FILE1 INCLUDE SBTEST10.FILE2 $DATA02 RESET VOLUME If you did not use the RESET VOLUME command above, then the INCLUDE lists for $DATA01 and $DATA02 are as follows: $DATA01 MYSUBVOL.MYFILE MMTEST10.FILE1 MMTEST10.FILE2 $DATA02 MYSUBVOL.MYFILE MMTEST10.FILE1 MMTEST10.FILE2 SBSUBVOL.
In the above example, the INCLUDE clause specifies that only audited files in $DATA01.MMTEST10 are to be replicated. The INCLUDEPURGE clause specifies that every Enscribe purge operation involving files in this same subvolume are to be replicated, but the EXCLUDEPURGE clause specifies that any purge operations involving the file $DATA01.MMTEST10.FILE10 are NOT to be replicated. Error Checking Extensive checking is done when the subvolume and file names are parsed, and invalid names cause errors.
Table 16 Replicating purge operations with INCLUDE, EXCLUDE, INCLUDEPURGE, and EXCLUDEPURGE (continued) INCLUDE Defined EXCLUDE Defined INCLUDEPURGE EXCLUDEPURGE Defined Not Defined Purge Operation Processing • The RDF extractor checks if INCLUDEPURGE has entries. If no matching entry is found, the purge operation is filtered. • The RDF extractor checks if a matching entry is found in the INCLUDEPURGE list and if the INCLUDE list has a file/fileset. If yes, the purge operation is not filtered.
12 Subvolume Name Mapping RDF allows users to replicate data from primary system source subvolumes to differently named destination subvolumes on the backup system. However, the recommended configuration is still one-to-one mapping between source subvolumes on the primary system and their corresponding destination subvolumes on the backup system. One-to-one mapping ensures that each partition of a partitioned file or table is mapped to the correct backup subvolume.
• Node names are not allowed in mapping strings. • Volume names are not allowed in mapping strings. If the updater detects a $ character, it logs an error. • Reserved names are not allowed in mapping strings. See the examples of invalid mapping strings listed below. • When two or more mapping rules are present in a mapfile, the rule listed first always takes precedence if it fits. For example, assume these two mapping strings are present: MAP NAMES SUBVOL1.* TO SUBVOL2.* MAP NAMES SUBVOL*.
How an Updater Manages Filename Collisions If you inadvertently map two subvolumes on the primary system to the same subvolume on the backup system for an updater, the updater detects the filename collision, logs EMS event 927, and abends. This approach prevents possible data corruption or disk failure. To illustrate how a filename collision might occur, assume that the mapping string for the updater that replicates from $DATA01 on the primary system to $DATA01 on the backup system is: MAP NAMES TEST1.
In this example, $DATA01 is the name of the volume on the primary system, and MAPLOG is the keyword. Because MAPLOG is followed by end of line, it indicates that the maplog file on the backup system be turned off. You can also alter the maplog file to a different path. For example: ALTER VOLUME $DATA01 MAPLOG $DATA05.NAPCONFG.MAPLOG2 If a maplog is not properly constructed or formatted, the updater generates errors.
To illustrate this problem scenario, assume these circumstances: • You create an audited, partitioned, key-sequenced file (Enscribe, SQL/MP, or SQL/MX) on the primary system where the primary and secondary partitions are on the same subvolume at $DATA01.SVOL.FILE and $DATA02.SVOL.FILE. • One updater replicates the changes for the primary partition $DATA01.SVOL.FILE on the primary system to $DATA11.SVOL1.FILE on the backup system using this mapping string: MAP NAMES SVOL.* TO SVOL1.
13 Auxiliary Audit Trails In addition to the Master Audit Trail (MAT), RDF/IMPX and ZLT support protection of up to 15 auxiliary audit trails. If you want to protect data volumes associated with an auxiliary audit trail, you must configure an auxiliary extractor and an auxiliary receiver for that trail. Thus, for each auxiliary audit trail, there will be one auxiliary extractor-receiver pair. Auxiliary Extractor An auxiliary extractor can only be configured to a single auxiliary audit trail.
• It is an error if the specified atindex does not correspond to a valid index of a configured auxiliary audit trail. That is, if you have configured two TMF auxiliary audit trails with the respective audit trail numbers of 1 and 2, you cannot configure an auxiliary extractor with an atindex value of 3. • It is an error to specify two extractors or two receivers with the same atindex value.
the TMF shutdown operation proceeds. The same can happen to the updaters when a stop-update-to-time or a SQL shared access DDL operation enters the RDF subsystem, wherein the updaters configured to an auxiliary audit trail may take a long time to shutdown if the auxiliary extractor has fallen behind. When that extractor finally caztches up, the affected updaters are able to shutdown.
14 Network Transactions The RDF/IMPX and RDF/ZLT products are able to guarantee backup database consistency for transactions that update data residing on more than one RDF primary system. RDF/IMPX and RDF/ZLT can map the volumes being protected to both the MAT and auxiliary audit trails. NOTE: Network transaction processing is currently not supported in configurations that use the triple contingency feature. You must use RDF/IMPX or RDF/ZLT to protect all databases open to network transactions.
NETWORKMASTER Attribute This attribute, located in the RDF configuration record, specifies whether or not the particular system is the master of the RDF network. Each RDF network has one, and only one, network master. To set this attribute, use this RDFCOM command: SET RDF NETWORKMASTER {ON | OFF} When this attribute is set to OFF (the default value), the particular system is not the network master. When this attribute is set to ON, the particular system is the network master of the RDF network.
REMOTECONTROLSUBVOL (RCSV) Network Attribute The remote control subvolume (RCSV) is the name of the control subvolume used by the RDF subsystem configured for the specified primary and backup systems. It is set by this RDFCOM command. SET NETWORK REMOTECONTROLSUBVOL subvolume-name There is no default value. PNETTXVOLUME Network Attribute You only use this attribute when configuring the network master.
(except the RDFNET process within the network master primary system) interacts with any other RDF subsystem in the RDF network. Therefore, the performance of an individual RDF subsystem is unaffected by its inclusion within an RDF network. RDF Takeovers Within a Network Environment With RDF/ZLT, no committed data from any primary system in the RDF network is lost. The discussions that follow regarding loss of data in a network takeover only apply to non-RDF/ZLT environments.
The purger of the network master determines what network transactions are incomplete across the different backup systems, and it produces the master network undo list. Each purger then uses this master list to ascertain the transaction data that must be undone on its backup database. For example, if a network transaction involved only four of the ten primary systems in an RDF network, then that transaction only needs to be undone on the backup databases where that data was replicated.
operation on the primary system. If, however, “kept-commits” have been encountered during phase 2 processing, a File Recovery position is not available; this is reported in RDF event 858. This last situation will never occur in an RDF/ZLT environment because a File Recovery position is always available with RDF/ZLT. If an RDF event 888 is reported, then the specified File Recovery position is based on both phase 1 and phase 3 processing. Each system logs its own File Recovery position.
7. 8. 9. 10. 11. 12. T13 T13 T14 T15 T14 T15 (network transaction started on \B) commit (non-network transaction) (network transaction started on \A) commit commit At approximately the same time system \B executes: 1. T10 (network transaction started on \A) 2. T20 (non-network transaction) 3. T12 (network transaction started on \A) 4. T13 (network transaction started on \B) 5. T21 (non-network transaction) 6. T22 (non-network transaction) 7. T36 (network transaction started on \C) 8. T21 commit 9.
that is where T102 originated. Thus, on \M, the sequence of commit records on the audit trail will likely be T101 followed by T102, whereas on \N it will likely be T102 followed by T101. For these two reasons, we can be certain T101 and T102 did not alter the same data: • Transaction record locking would have prevented these transactions from altering the same data.
5. 6. 7. When all other RDF subsystems in the RDF network list 0:00 extractor RTD times, issue the RDFCOM START RDF command on the system where you had stopped RDF. Perform your shared access NonStop SQL/MP DDL operation on your primary system. Follow the normal method for replicating shared access NonStop SQL/MP DDL operations on your backup system.
special file on its PNETTXVOLUME volume. If the communications line to one of those primary systems is down, and you then issue a STOP RDF command on the network master’s primary system, the STOP RDF command could appear to hang. The reason for this is that the RDFNET process might be trying to open a file for the system whose path is down. In such a case, the RDFNET process waits until either the line comes back up or the Expand level-4 timer expires.
ADD RDF SET SET SET ADD MONITOR CPUS 1:2 MONITOR PRIORITY 185 MONITOR PROCESS $MMON MONITOR SET SET SET SET SET ADD EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR SET SET SET SET SET SET SET ADD RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER SET SET SET SET SET ADD PURGER PURGER PURGER PURGER PURGER PURGER ATINDEX 0 CPUS 1:2 PRIORITY 185 PROCESS $MEX1 RTDWARNING 60 ATINDEX 0 CPUS 3:2 EXTENTS (100,100) PRIORITY 185 RDFVOLUME $DATA11 FASTUPDATEMODE OFF PROCESS $M
SET SET SET SET SET SET SET SET SET ADD RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF SOFTWARELOC $SYSTEM.
Control Subvol: $SYSTEM.
15 Process-Lockstep Operation The RDF/IMPX products include the process-lockstep operation, which is process-based. That is, when a process invokes the lockstep operation for a business transaction, the process must wait until all audit records associated with that business transaction are safely stored in image trails on the backup system before continuing. Process-lockstep is not needed with RDF/ZLT because ZLT functionality provides means whereby no committed data is ever lost during an unplanned outage.
The DoLockstep Procedure How you invoke the DoLockstep procedure differs depending on whether your applications are written in COBOL or TAL. Including the DoLockstep in COBOL85 Applications To invoke the DoLockstep procedure from a COBOL85 program, you must first include the DoLockstep object module in the SPECIAL-NAMES paragraph in the CONFIGURATION section. CONFIGURATION SECTION. SOURCE-COMPUTER. HP NONSTOP. OBJECT-COMPUTER. HP NONSTOP. SPECIAL-NAMES. FILE "$vol.subvol.LSLIBTO" IS LOCKSTEP-LIB.
RDF receiver has flushed all audit records up to and including the lockstep audit into the image trail, it replies to the extractor that the lockstep data is safe. When the extractor receives that information, it replies to the gateway which, in turn, passes status back to the DoLockstep call, and the latter then returns status to the application.
Multiple Concurrent Lockstep Operations Because DoLockstep suspends the calling application until the associated lockstep transaction commits on the backup system, a single application process cannot have more than one lockstep operation in progress at any one time. Multiple application processes, however, can invoke DoLockstep concurrently.
STARTUPMSG This attribute must include the process name of your RDF extractor (for example, STARTUPMSG "ENABLE $MEXT"). The startup message must also include either ENABLE or DISABLE as the first parameter. Failure to include either of these parameters will cause the gateway to stop. The gateway can only communicate with one extractor. If you have multiple RDF subsystems using the same node as their primary system, only one of them can execute lockstep operations.
request must wait to be performed until the current lockstep transaction is committed on the backup system. That could also increase response times. Lockstep and Auxiliary Audit Trails You cannot use lockstep processing in an RDF subsystem that is protecting auxiliary audit trails. Lockstep and Network Transactions You cannot use lockstep to protect data associated with network transactions because the lockstep protocol only pertains to operations on a single system.
Effect The lockstep gateway stops. Recovery In your SCF script for starting the lockstep gateway, you must specify either ENABLE or DISABLE as the first argument of the STARTUPMSG attribute. 4 The lockstep gateway has received error errnum when attempting to communicate with the RDF extractor procname. errnum is a file-system error number. procname is the name of an extractor process. Cause The RDF extractor is no longer responding, and it might be stopped. Effect The lockstep gateway stops.
Cause When the gateway attempted to create the specified lockstep file, it received the specified error. Effect The lockstep gateway stops. Recovery Correct the error condition and restart the lockstep gateway. 7 Open error errnum on filename. errnum is a file-system error number. filename is the name of a lockstep file. Cause The lockstep gateway received the specified error while attempting to open the specified lockstep file. Effect The lockstep gateway stops.
Effect The lockstep gateway stops. Recovery Correct the error condition and restart the lockstep gateway. 10 The RDF lockstep file filename has an incorrect file code. filename is the name of a lockstep file. Cause The specified lockstep file has the wrong file code. Effect The lockstep gateway stops. Recovery Either the file was not created by the lockstep process, or the file code was incorrectly altered. Purge the file and restart the lockstep gateway. 11 Lockstep file filename is not audited.
Cause The lockstep gateway sent a request to the RDF extractor, and the latter returned invalid data. Effect The lockstep gateway stops. Recovery This is an internal error, but the gateway is restarted. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC) or your service provider. 14 BEGINTRANSACTION error errnum when attempting a lockstep transaction. errnum is a file-system error number. Cause The gateway encountered the specified error on BEGINTRANSACTION.
17 Open error errnum on $RECEIVE. errnum is a file-system error number. Cause The lockstep gateway received the specified error when attempting to open $RECEIVE. Effect The lockstep gateway stops. Recovery This is an internal error, but the gateway is restarted. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC) or your service provider. 18 Filename formatting error errnum. errnum is a file-system error number.
Recovery This is an internal error, but the gateway is restarted. If the problem persists, contact the Global Mission Critical Solution Center (GMCSC) or your service provider. 21 Invalid process name procname for the RDF extractor. procname is the invalid process name. Cause You have specified a node name with the name of the extractor in your SCF script. Effect The lockstep gateway stops. Recovery You must remove the node name for the extractor from your SCF script.
24 Error errnum returned when attempting to lock the lockstep file filename. errnum is a file-system error number. filename is the name of a lockstep file. Cause The specified error was returned when the lockstep gateway attempted to lock the specified file. Effect The lockstep gateway stops. Recovery SCF automatically restarts the gateway. If the problem persists and the autorestart count is exhausted, correct the condition that caused the error and then restart the gateway.
28 RDF extractor procname responded with error errnum to lockstep request. procname is the name of an extractor process. errnum is a file-system error number. Cause While the extractor is processing a lockstep request, the gateway stops, has been restarted by SCF, and has sent a new lockstep request to the extractor. Effect The lockstep gateway stops. Recovery SCF automatically restarts the gateway.
Cause In your SCF script for starting the lockstep gateway, the process name specified in the STARTUPMSG attribute was not a valid process name for the RDF master extractor. Effect The lockstep gateway stops. Recovery Correct the STARTUPMSG attribute script and then manually delete the RDF lockstep gateway process from SCF and run your newly edited SCF script. The process name must not include a node name. 32 A spurious STARTUPMSG argument was encountered for the lockstep gateway.
16 NonStop SQL/MX and RDF RDF supports replication of NonStop SQL/MX user tables (file code 550) and indexes (file code 552). These operations are supported in much the same way as they are with NonStop SQL/MP, and the same types of data and DDL operations are replicated.
CREATE CATALOG BCAT LOCATION $DATA01; 3. If you want each catalog to be seen from both systems, register your primary and backup catalogs. To register the primary catalog on the backup system, issue a REGISTER CATALOG command on the primary system. To register the backup catalog on the primary system, issue a REGISTER CATALOG command on the backup system. The format of the REGISTER CATALOG command is: REGISTER CATALOG catalog ON node.
schema, you must use the same subvolume here. If you did not specify the LOCATION clause when creating the primary system's schema, you must query the primary system to obtain the Guardian subvolume name, and you must use the Guardian subvolume name with the LOCATION clause here. For example, if issued on the backup system, this command creates a schema on the backup system called SCH in catalog BCAT using subvolume ZSDXYZ3A: CREATE SCHEMA BCAT.SCH LOCATION ZSDXYZ3A; 6.
name but the Guardian filename will not normally be the same, even if the partitions are on different volumes. 7. Create each object on the backup system. The ANSI name of the object must be constructed as follows: • catalog name: use the name of the backup catalog you created in Step 2. • schema name: use the name you used in Steps 4 and 5. • table or index name: must match on the primary and backup systems. This command creates a table called TAB1 in the schema BCAT.
CREATE SCHEMA BCAT.SCH LOCATION ZSDXYZ3A; You must use the LOCATION clause. If you specified the LOCATION clause when creating the primary system's schema, you must use the same subvolume here.
6. At the backup system, use the RESTORE utility to place the objects on the backup system, specifying the ANSI names for the backup system. Use the LOCATION clauses to have RESTORE place the objects in the correct Guardian locations. See “Restoring to a Specific Location” for general restore syntax for NonStop SQL/MX databases. For example, assume you have the objects on your primary system that have these fully qualified Guardian names: \pnode.$DATA01.ZSDABCDEF.FILE100 \pnode.$DATA02.ZSDABCDEF.
described in “Creating a NonStop SQL/MX Backup Database From an Existing Primary Database” (page 310) to generate the LOCATION clauses for the temporary objects, modifying the volume names as necessary and using the primary node name for the -node option. Alternatively, you can use the SHOWDDL command to obtain the fully qualified filenames of the objects you want replicated and specify the same Guardian subvol.filenames in the corresponding LOCATION clauses when creating the temporary objects.
The backup database is now ready for RDF replication, and you can drop the temporary catalog.schema.objects on your primary system. Creating the Fuzzy Copy on the Backup System The advantage of this method is that it eliminates the use of temporary objects as well as tape handling because you create your backup objects directly on the backup system.
Indirectly From the Primary to the Backup By Way of a Temporary File If the number of rows to load over the network is too great, you can use a temporary file on the primary system: 1. Create a temporary catalog on your primary system to correspond to your regular catalog on your primary system whose objects you want RDF to replicate. 2. Create a temporary schema for your temporary catalog. Follow the instructions given above in “Creating a NonStop SQL/MX Backup Database From an Existing Primary Database”.
and then load the data into the backup partition using the INSERT statement also described in that topic. Correcting Incorrect NonStop SQL/MX Name Mapping Primary and Backup ANSI Catalog Are the Same If you created the primary and backup catalogs and used the same name for both, you cannot use the REGISTER CATALOG command to make either catalog visible on the other system.
necessarily correspond to the sequence in which the user specifies columns on CREATE TABLE.
4. 5. 1. 2. You are restoring four tables from two different schemas in catalog PCAT. Schema information: Primary schema name Schema subvolume Backup schema name PCAT.MYSCHEMA ZSDAAAAA BCAT.MYSCHEMA PCAT.MYSCHEMAX ZSDBBBBB BCAT.MYSCHEMAX Table and Index information: Table or Index Name Guardian Names for partitions and indexes PCAT.MYSCHEMA.MYTABLE1 PCAT.MYSCHEMA.MYINDEX1 \P.$data01.ZSDAAAAA.HEBFRW00 \P.$data02.ZSDAAAAA.HEBFRX00 \P.$data03.ZSDAAAAA.HEBFRY00 \P.$data02.ZSDAAAAA.YREWPO00 PCAT.
Comparing NonStop SQL/MX Tables While the unsupported RDFCHEK utility program can be used to compare Enscribe files or NonStop SQL/MP tables, it cannot be used to compare NonStop SQL/MX tables. If you need to compare a NonStop SQL/MX table on your primary against a NonStop SQL/MX table on your backup system, for example, one method of doing so is as follows: 1. Use the NonStop SQL/MX Select statement to select all rows in the primary table, and then store them in an Enscribe entry-sequenced file. 2.
17 Zero Lost Transactions (ZLT) Zero Lost Transactions (ZLT), functionality that is available only with the RDF/ZLT product, ensures that no transactions that commit on the primary system are lost on the RDF backup system if that primary system is downed by an unplanned outage. RDF achieves this though the use of remote mirroring for the relevant TMF audit trail volume(s).
Figure 13 ZLT Configuration With a Single Standby/Backup System Figure 14 shows the configuration where a single system serves as both the standby and backup systems, and the remote mirror is located at an intermediate site. Figure 14 ZLT Configuration With a Single Standby/Backup System and With the Remote Mirror Located at an Intermediate Site Figure 15 shows the configuration where individual standby and backup systems are located at separate sites.
Figure 15 ZLT Configuration With Standby and Backup Systems Located at Separate Sites If the standby and backup systems are not one and the same, you must remember to set up remote passwords between the standby and backup systems. You must do so with the same user ID that has control over starting and stopping RDF. If you lose your primary system due to an unplanned outage, you connect the remote mirrors to the standby system, and then initiate a takeover operation on the backup system.
If CommitHoldMode mode is activated, TMF stops all further commit operations. Because transactions on the primary system cannot commit or abort while the remote mirror is unavailable, you achieve ZLT protection if you should lose your primary system while commit-hold mode is activated. When such an event occurs, however, transaction processing on the primary system effectively stops. TMF provides another configuration attribute associated with CommitHoldMode: COMMITHOLDTIMER.
RDF Configuration Attributes RDF Remote Mirror Configuration When declaring the attributes of the RDF configuration record, you use this optional attribute to specify whether ZLT is enabled or disabled: SET RDF REMOTE MIRROR [ ON | OFF ] The default is off. If this attribute is off, normal RDF operations are unchanged, as is execution of the RDF TAKEOVER command.
When you ADD the extractor attributes, RDFCOM checks to ensure that each configured volume is a valid volume. If any are not, the ADD command fails with an error for the first volume name that is either an invalid name or does not correspond to a valid volume. ALTER RDF Remote Mirror Configuration You can alter the RDF REMOTE MIRROR configuration attribute to turn ZLT protection on and off as needed. If entered on the primary system, you must stop RDF, alter the attribute, and then restart RDF.
The Audit-Fixup Process The audit-fixup process only ever runs on the remote standby system in an RDF/ZLT environment and typically lasts only a few seconds. The audit-fixup process performs file-fixup operations on audit trail files on the remote mirror that have been left with the CRASHOPEN flag set following a failure of the RDF primary node. The audit-fixup process is started by an extractor whenever the extractor attempts to read an audit trail file that has the CRASHOPEN flag set.
Old Audit-Trail Files When a ZLT takeover operation completes, you should not purge the old audit trail files on the remote mirrors connected to the standby system if you believe you can recover the primary system. The old audit trail files are necessary for recovering the primary system. If you can’t recover the primary system, you might purge the files because they have no further use.
2. Recover the database on your former primary system. How you do this depends upon whether local disks or remote mirrors received the most audit records (which you determined in the preceding step). CommitHoldMode ON If all of the remote mirrors (MAT and all auxiliary audit trails) have more or the same number of audit records as the local disks (this typically happens if CommitHoldMode was configured and enabled on the primary system when the outage occurred): a.
During ZLT Takeover Processing During Phase 1 of the ZLT Takeover processing, the shutdown audit-record is not stored in image trails, and the RDF processes continue running. The goal of ZLT processing is to catch up data as quickly as possible. Thus, there is no point in stopping RDF processes if a STOP TMF record is found in the master audit trail (MAT).
A RDF Commands Quick Reference The syntax rules for the RDFCOM and RDFSCAN commands, explained in detail in Chapter 8 (page 176) and Chapter 9 (page 250), are summarized in this appendix. This appendix, which is written for system managers and operators, summarizes the syntax descriptions for: • The command to run RDFCOM from the Guardian user interface to the NonStop operating system. See “RDFCOM Run Syntax”. • The RDFCOM commands, listed in alphabetical order, beginning with the ADD command.
{RECEIVER {PURGER {RDFNET {TRIGGER {VOLUME receiver-option } purger-option } netsync-option } {trigger-type } {trigger-option } } updater-option } COPYAUDIT The COPYAUDIT command copies missing audit records from the backup system that has the most to the backup system that has the least. This command is only for use with the triple contingency feature. Where Issued: Backup system only (the backup system with the least amount of audit records).
Security: Any user. HISTORY INFO The INFO command displays the current configuration parameter values from the configuration file for the specified process or other object. Where Issued: Primary or backup system. Security: Any user.
Security: Any user. OUT [\system.][$volume.][subvolume.][file] RESET The RESET command resets all configuration parameters for the specified process to their default values within the RDF configuration memory table. The corresponding parameters within the configuration file do not change, however, unless you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
{PRIORITY priority {PROCESS process-name } } SET NETWORK The SET NETWORK command sets RDF network configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD NETWORK command. Where Issued: Primary system only. Security: Super-user group member.
SET RDFNET The SET RDFNET command sets the designated configuration parameters for the RDFNET process to the supplied values within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
where volume-option is: {ATINDEX atindex {CPUS primary-CPU : backup-CPU {PRIORITY priority-number {PROCESS process-name {IMAGEVOLUME volume {UPDATEVOLUME volume {INCLUDE subvol.file {EXCLUDE subvol.file {INCLUDEPURGE subvol.file {EXCLUDEPURGE subvol.file {MAPFILE $vol.subvol.file {MAPLOG $vol.subvol.file } } } } } } } } } } } } SHOW The SHOW command displays the current parameter values contained in the RDF configuration memory table for the specified process.
{RTDWARNING {RDFNET } } STOP RDF The STOP RDF command shuts down the RDF subsystem. Where Issued: Primary or backup system (can be issued on the backup system only when all communications lines to the primary system are down). Security: Super-user group member with remote password from the primary system to the backup. STOP RDF { [, DRAIN ] } { [, REVERSE ] } STOP SYNCH The STOP SYNCH command is used as part of the online database synchronization protocol.
Where issued: primary or backup system. Security: Any user. RDFSCAN [ file ] AT The AT command specifies the record in the RDF log file at which RDFSCAN begins the next operation. AT [record-number] DISPLAY The DISPLAY command enables or disables the display of line (record) numbers in subsequent RDFSCAN output. DISPLAY {ON | OFF} EXIT The EXIT command ends your current RDFSCAN session. EXIT FILE The FILE command selects the RDF log file to which subsequent RDFSCAN commands apply. FILE [\system.
SCAN The SCAN command scans a specific number of messages in the log file and displays all of those in that range that contain the current match pattern. SCAN number File Names and Process Identifiers File names and process identifiers sometimes appear as parameters in RDFCOM and RDFSCAN commands. These names typically identify objects such as disk files, log devices, and processes. Reserved File Names Subvolume names that begin with the letter “Z” are reserved.
B Additional Reference Information This appendix provides additional reference information about: • “Default Configuration Parameters” (page 340) • “Sample Configuration File” (page 341) • “RDFSNOOP Utility” (page 343) • “RDF System Files” (page 343) • “RDF File Codes” (page 345) Process names are also reserved: $X* , $Y* , and $Z*. Certain keywords in the NonStop SQL/MP product are reserved words in SQL commands. Those reserved words are listed in the SQL/MP Reference Manual.
Parameter Default Value(s) MIN MAX RECEIVER FASTUPDATEMODE off n.a. n.a. TRIGGER CPUS 0:1 0 15 TRIGGER PRIORITY 150 10 199 TRIGGER WAIT WAIT n.a. n.a. TRIGGER NOWAIT WAIT n.a. n.a. PURGER CPUS 0:1 0 15 PURGER PRIORITY 165 10 199 PURGER PURGETIME 60 30 1440 PURGER RETAINCOUNT 2 2 5000 VOLUME ATINDEX 0 0 15 VOLUME CPUS 0:1 0 15 VOLUME PRIORITY 160 10 199 VOLUME UPDATEVOLUME $SYSTEM n.a. n.a. VOLUME IMAGEVOLUME RECEIVER RDFVOLUME n.a. n.a.
SET RECEIVER PRIORITY 165 SET RECEIVER RDFVOLUME $GOLD SET RECEIVER FASTUPDATEMODE ON SET RECEIVER PROCESS $MRECV | *** | *** Add the receiver parameters to the | *** RDF configuration file. | *** ADD RECEIVER| *** | *** Add secondary image trails. | *** ADD IMAGETRAIL $SECIT1 ADD IMAGETRAIL $SECIT2 | *** | *** Set the updater parameters for the first | *** volume to be protected by the RDF product. | *** $U01 is the name of this updater.
| *** Note that the IMAGEVOLUME parameter is omitted; | *** it defaults to $SECIT2 because it was not reset | *** after the previous ADD VOLUME command. | *** SET VOLUME CPUS 2:1 SET VOLUME PRIORITY 160 SET VOLUME UPDATEVOLUME $DB3 SET VOLUME PROCESS $U03 | *** | *** Add the RDF updater parameters for | *** the third updater process to the | *** configuration file. | *** ADD VOLUME $DB03 RDFSNOOP Utility RDFSNOOP is a utility that is used to examine image file records pointed to by RDF exception files.
$SYSTEM.control-subvolume.CONFIG • Context file The context file is a key-sequenced file with record length 4062. The context file contains the context information that tells the RDF subsystem where the RDF processes stopped. There is a separate context file on the primary node and the backup node; on both nodes, the context file is named: $SYSTEM.control-subvolume.
• RDFTKOVR file This file records whether an RDF Takeover operation has completed successfully. This file is empty under normal circumstances (eof = 0). If, however, you have executed an RDF Takeover operation and it completes successfully, then they key word "DONE" is written in the file by RDF. This file can be used for executing fast business takeover operations. See “How to Plan for the Fastest Movement of Business Operations to Your Backup System After Takeover” (page 135) for more details.
C Messages This appendix describes the messages generated by RDF.
on the sending system. (3) The name of the system on which the particular RDF process is running. (4) The name or process ID of the RDF process that issued this message. (5) The message number. (6) The message text that explains the log entry. If the EMS event log is $0 (the default collector), only items (3), (4), (5) and (6) are logged because of file-length restrictions. The pages that follow list all the RDF messages that RDF produces. The messages appear in ascending order by message number.
Effect Variable; depends upon the process and the particular error, it might be retried or it might cause RDF to abort. Recovery Correct the error reported in the message and if RDF aborted, restart RDF. 702 Program version is inconsistent program expected-expected received-received program is the name of the program file that RDF tried to execute. expected is the expected version number of the program. received is the actual version number of the program, as reflected by the program file.
705 File Open Error error on [ANSI-object-typeANSI-name, Partition partition-id,] file filename error is the file-system error number that identifies the specific error. ANSI-object-type is the ANSI object type (for example, table, index, and so on). ANSI-name is the ANSI name of the SQL/MX object that encountered the error. partition-id is the partition ID of the SQL/MX object that encountered the error. filename is the Guardian file name of the file that encountered the error.
707 TMF is not yet started Cause The extractor detected that TMF has not been started yet. Effect RDF cannot run if TMF is not also running. Normally RDFCOM will recognize that TMF has not been started and will prevent RDF from starting. In the case of an RDF 707 event, TMF was running when RDFCOM verified that TMF was started, but TMF was then stopped before the extractor was started. If the extractor detects that TMF is not started, it aborts itself, and the monitor aborts the receiver and itself.
Cause The updater failed to obtain process information about itself. This is a fatal error. Effect The updater process abends. Recovery This is an internal error. Contact your service provider. 712 Process creation error nnn nnn, file filename nnn nnn are the upper and lower bytes, respectively, of the status code reported by the NEWPROCESS procedure. filename is the name of the program file that was to be executed. Cause The monitor encountered an error while attempting to create an RDF process.
error is the file-system error number that identifies the specific error. Cause A call to the checkpoint procedure failed, and the backup process of a NonStop process pair is still running. The message includes the number of the file-system error that was encountered when the primary process was trying to communicate with the backup process. Effect The backup process is stopped, and a new one is created after about 15 seconds.
Cause The original backup process of a NonStop process pair has successfully created a backup process in the configured primary processor and has successfully switched processing to that process. Effect The NonStop process pair is switching primary and backup roles so that the primary process is now running in the CPU configured as the primary processor. Recovery This is an informational message; no recovery is required.
Tell your database administrator that this error occurred. The database administrator should consider checking the synchronization of the primary and backup databases. 722 Waiting for audit trail file restoration, SNO sno sno is the sequence number of the audit trail for which the extractor is waiting. Cause The extractor has requested that the specified audit trail file be restored. Effect The extractor waits until the audit trail file is restored.
failure or a STOP command entered manually from TACL. Because the updater might not have processed all image audit, the RDF TAKEOVER operation cannot be considered complete. Scan the EMS event log for RDF message 726: this message identifies the updater process that did not complete TAKEOVER processing. Effect Normal purger shutdown processing continues. Recovery If UPDATE was OFF at the time of the RDF TAKEOVER, then a second RDF TAKEOVER operation is automatically started, and no recovery is required.
priority is the priority requested for the process. Cause An attempt to alter the priority of an RDF process to the indicated priority has failed. Effect The process continues to run at its current priority. Recovery This is an informational message; no recovery is required. Reissue the ALTER command. 730 Process priority altered priority priority is the priority requested for the process. Cause The operator successfully changed the priority of an RDF process to priority.
filename is the Guardian file name of the file that is affected by the DDL operation. Cause The updater has found a Stop-RDF-Updater record in the image trail. This special record is generated in the TMF audit trail on the primary system when an SQL DDL operation WITH SHARED ACCESS involving the specified file has completed. Each updater will stop when it reaches this record in the image trail. Effect The updaters stop.
Cause The purger logs this message after the successful completion of an RDF takeover operation. • If all data volumes on the primary system are configured to the MAT, then the reported position is the end of the last record received from the extractor. • If any data volumes on the primary system are configured to auxiliary audit trails, then the reported position is the end of the last commit or abort record received from the extractor for which no data from any auxiliary audit trail is missing.
738 RDF extractor synch established SNO sno RBA rba sno is the sequence number of the TMF Master Audit Trail (MAT) for which the synchronization point was established. rba is the relative byte address of the synchronization point. Cause This message indicates that the receiver has sent the extractor a starting position in the TMF audit trail, and that the extractor has thereby become synchronized with the receiver. Effect Extractor is synchronized with the receiver.
Either the file must be redefined on the primary node, or the other volume must be made protected by RDF. In the latter case, the backup file must then be resynchronized with the primary file. 741 RDF extractor message out of order Cause The receiver has received a message from the extractor that is out of order. When this event occurs, the extractor automatically reestablishes synchronization with the receiver.
filename is the Guardian file name of the file that encountered the error. Cause The updater was previously delayed in obtaining information about the specified object. See RDF error 736. The information has now been obtained. Effect The updater continues processing. Recovery This is an informational message; no recovery is required. 745 Audit record conversion error error error is the error number.
748 Internal error - RDF extractor abending Cause The extractor has detected an audit record of an unknown version. Effect The extractor process abends. Recovery This is an internal error. Contact your service provider. 749 Old audit record format encountered Cause The extractor has detected an audit record generated by an unsupported version of TMF. Effect The extractor abends. Recovery Reinitialize RDF. You might need to resynchronize the primary and backup databases.
Recovery See the description of the FILE_OPEN_CHKPT_ procedure in the Guardian Procedure Calls Reference Manual to determine the cause of the failure. If possible, correct the underlying cause to avoid its reoccurrence. 752 Audit block RBN out of sequence. File filename RBN rbn RBA rba filename is the name of the audit trail file that contained the error. rbn is the relative block number of the block where the error occurred in the audit trail file.
Effect Processing continues from the point at which the network failed. Recovery This is an informational message; no recovery is required. 755 CHECKMONITOR failure - backup abended Cause The primary process of a process pair stopped after creating its backup process, but before completing the backup initialization. Effect This is a catastrophic error; the process abends, and RDF stops. Recovery Restart the RDF product and report the error to your service provider.
759 Secondary partition on unknown node filename filename is the name of the affected file. Cause An updater has encountered an audit record associated with either an Enscribe create, an increase of MAXEXTENTS for an Enscribe file, or a PURGEDATA operation for an Enscribe file, and the file on the primary system has secondary partitions that are located on different systems in the network. Effect The updater skips this record.
Recovery Purge all existing context and configuration files on the primary and backup system. Then initialize the RDF subsystem. 763 Process incompatible with local system Cause The process reporting the error has determined that it has been installed on the wrong operating system. Effect The process abends. Recovery Install the version of the RDF product that is compatible with the installed release of the operating system.
Effect The extractor continues with processing the second part of phase one. Recovery This is an informational message; no recovery is required. 767 Phase one part 2 database synchronization complete Cause The second part of phase one of a database synchronization operation has completed. Effect The extractor continues with the third part of phase one. Recovery This is an informational message; no recovery is required.
Cause The receiver has successfully completed its initialization. Effect The receiver is prepared to receive data from the extractor. Recovery This is an informational message; no recovery is required. 772 TMF is not running on the remote system Cause The receiver has determined that TMF is not started on the RDF backup system. Effect The receiver abends. Recovery Start TMF on the backup system and then restart RDF.
Recovery This is an informational message; no recovery is required. 776 Remote RDF receiver shutdown complete Cause The receiver has terminated normal processing as the result of a STOP TMF, STOP RDF, or TAKEOVER command. Effect Normal RDF shutdown processing continues. Recovery This is an informational message; no recovery is required. 777 Unexpected STOP SYNCH message received Cause The extractor has received a STOP SYNCH message, but it is not involved in a database synchronization operation.
filename is the name of the exception file. Cause An updater is unable to apply image records for some transactions because a TAKEOVER command was executed and the commit, abort, or data records for the transactions were not sent to the backup system. The message includes the name of the exception file containing information about the image records that were not applied. Effect If all the records for a transaction are not received on the backup node, the transaction is treated as if it aborted.
Effect If the monitor or extractor process receives a file-system error 14 (process does not exist), RDF will shut down on the primary node. Recovery If RDF was stopped on the remote node by a STOP RDF command while the communications lines were down, simply restart RDF by issuing a START RDF command. 784 Shutdown pending STOP UPDATE, TIMESTAMP timestamp timestamp is the specified timestamp. Cause The process has received notice that an RDFCOM STOP UPDATE, TIMESTAMP command was executed.
filename is the name of the image trail file that contained the error. sno is the sequence number where the error occurred. rba is the relative byte address where the error occurred. Cause The receiver or an updater has encountered the indicated error while attempting to position into an image file. Effect The process abends. Recovery Correct the problem that caused the error and then restart RDF. 788 ALLOCATESEGMENT failure.
Effect The primary process will now run in fault-tolerant mode. Recovery This is an informational message; no recovery is required. 796 Image file creation error error on filename error is the file-system error number that identifies the specific error. filename is the name of the image file associated with the error. Cause The receiver or purger process could not create the specified file due to the specified file-system error. Effect This is a catastrophic error; the process abends and RDF stops.
798 Image trail file open error error on filename error is the file-system error number that identifies the specific error. filename is the name of the image file associated with the error. Cause An RDF process encountered the specified file-system error while attempting to open the specified file. Effect The process abends, and RDF stops. The exception to this is an error 12 (file in use) issued when either the receiver or purger attempts to open the file.
Effect The message includes the error number returned by the WRITE system procedure followed by the file name. For error 43 (unable to obtain disk space for extent), the receiver retries the write operation. All other errors are fatal; the receiver abends, and RDF stops. Recovery The only recovery from an error 43 condition is to free some disk space.
Recovery You should determine the cause of the error and take appropriate corrective action. 804 READUPDATELOCK error error on filename error is the file-system error number that identifies the specific error. filename is the name of the file on which the error occurred. Cause The RDFNET process has encountered the specified error on the specified file. Effect The RDFNET process aborts its current transaction, posts a timer, and waits for that timer to expire before attempting a new transaction.
Recovery This is an informational message; no recovery is required. 808 Update mode has been set OFF Cause The operator issued a STOP UPDATE command. Effect RDF stops updating the backup database. Recovery This is an informational message; no recovery is required. 809 Shutting down in response to STOP RDF Cause The operator issued a STOP RDF command. Effect The RDF process stops normally. Recovery This is an informational message; no recovery is required.
Cause The updater encountered a file-system error while attempting to communicate with the receiver or purger. The file-system error number and the name of the receiver or purger are included in the message. Effect This is a catastrophic error; the updater abends, and RDF will abort. Recovery Determine the cause of the error. If the receiver or purger did not abend, correct the condition, and restart RDF.
816 Image trail file SETMODE error error on filename error is a file-system error number. filename is the name of the image file associated with the error. Cause The receiver or purger process has encountered an error while attempting to perform a setmode operation on the specified file. Effect The process abends. Recovery Correct the problem that led to the error and restart RDF.
Recovery A subsequent warm start of RDF might be possible, but the success of the restart depends on the nature of the failure that caused the original process to stop. If the message is issued during ZLT processing, no recovery is required. 820 RDF receiver stopped unexpectedly, receiver receiver is the name of the receiver process that stopped. Cause The receiver has stopped unexpectedly. The message includes the name of the stopped process. Effect This message is issued by the RDF monitor.
transaction marked for undo on a different node in the RDF network. Note, however, that this transaction could still be undone during final checking for business consistency across all backup nodes. Effect This is an internal event. There is no effect. Recovery This is an informational message; no recovery is required. 824 Missing RDF extractor config record, ATINDEX audit-trail-index Cause The RDF monitor was unable to find an extractor configuration record when performing a START RDF command.
828 Killing backup process ... Cause The primary process of a process pair has detected a problem in communicating with the backup process. An earlier message will have indicated the communications problem. Effect Because of the severity of the problem, the primary process attempts to stop the backup process. If the backup process stops, the primary process then attempts to create a new backup process. Recovery This is an informational message; no recovery is required.
You might be able to correct the underlying problem and restart RDF. Otherwise it might be necessary to reinitialize RDF. 832 Open error error on filename error is the file-system error number that identifies the specific error. filename is the name of the affected file. Cause The RDFNET process obtained the specified error in attempting to open the specified file. Effect The RDFNET process restarts. Recovery You should determine the nature of the error and take corrective action.
835 RDFCOM csv command-text [ issued by userid ] csv specifies the RDF control subvolume of the affected RDF environment. command-text is the text of the command that was issued. userid if present, is the Guardian userid (group.user) of the user who issued the command. Cause RDFCOM logs this message whenever you issue any of these commands: ALTER, INITIALIZE RDF, START RDF, START UPDATE, STOP RDF, STOP UPDATE, or TAKEOVER. command-text is the command text.
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 RDFNET process has terminated unexpectedly Cause The RDFNET process has terminated unexpectedly. Effect This message is issued by the RDF monitor.
841 Error - Unable to complete STOP UPDATE. Error error error is a file-system error number. Cause The monitor was unable to send a shutdown message to an updater because of the indicated file-system error. Effect The monitor terminates the attempt to send STOP UPDATE messages to any other updaters. It then sends an ABORT RDF message to all the other RDF processes and waits for them to stop.
845 Initialization synchronization completed Cause The updater that generated this message has completed its synchronization work for RDF initialization to an initialization timestamp. Effect The updater resumes its normal processing. Recovery This is an informational message; no recovery is required. 846 RDF TAKEOVER during database synchronization Cause When the updater completed its RDF Takeover operation, it had not yet completed its role in an online database synchronization.
Cause TMF was stopped during an RDF online database synchronization operation, before the extractor had completed its phase one processing. Effect The extractor abends because the database synchronization operation can no longer succeed. Recovery You must reinitialize the RDF product and restart the online database synchronization operation.
Recovery Contact your service provider for assistance with recovering from this situation. 854 ZTXUNDO file cannot be opened Cause While attempting to write the list of transactions that need to be undone to the ZTXUNDO file, that file could not be opened. Effect RDF aborts. Recovery If the operation involves an RDF takeover, take corrective action to enable the file to be opened and then reissue the TAKEOVER command.
858 A safe File Recovery position does not exist Cause A network takeover operation has completed, but, for this particular node in the RDF network, there is no safe MAT position with which you can issue a File Recovery operation on your primary system should that node become available again. Effect There is no effect. Recovery This is an informational message; no recovery is required. 859 Error error on BEGINTRANSACTION encountered error is an error number.
Cause The extractor has fallen behind the configured RTDWARNING threshold specified in the RDF configuration. Effect The extractor continues normal processing. Recovery This is an informational message. You should, however, try to determine why the extractor has fallen behind and take corrective action if necessary. 862 Updater processname RTD (rtd) exceeds RTD warning threshold (threshold#) processname is an updater process name. rtd is an RTD value. threshold# is an RTDWARNING warning threshold value.
865 Missing purger config record Cause The purger configuration record is not in the RDF configuration file. Effect The reporting process abends and RDF will abort. Recovery Restart RDF. If the problem persists, contact your service provider. 866 RDF purger stopped unexpectedly Cause The purger process has terminated unexpectedly. Effect RDF aborts. Recovery Determine why the purger stopped, and then restart RDF. If the problem persists, contact your service provider.
Recovery This is an internal error. Report this to your service provider. 872 Warning; Lockstep operation is denied Cause An application has attempted an RDF lockstep operation but you have not configured RDF for lockstep operations. Effect No lockstep operations can take place, and the lockstep gateway process abends. Recovery This is a warning. If you want lockstep operations, you must stop RDF and create a new RDF configuration with the RDF LOCKSTEPVOL attribute set.
Effect The process abends and RDF will abort. Recovery The file must be altered or recreated with the correct file format and then RDF can be restarted. 876 Imagetrail safe position: SNO sno RBA rba sno is the sequence number. rba is the relative byte address. Cause This is an imagetrail safe position. Effect This is an internal event. There is no effect. Recovery This is an informational message for historical purposes about a pending undo pass. No recovery action is required.
Effect The purger process will not process any more files in that particular subvolume. The operation will be attempted again after PURGETIME minutes. Recovery The file or table being reported was not created by RDF and is not part of the RDF environment. It must be manually purged or renamed out of the image subvolume before the purger process can continue normal processing.
Cause The named RDF process' current transaction has been aborted by TMF and the disk process. Effect The process restarts. Recovery This is an informational message. You must examine the event log to determine why the process is restarting and if any recovery action is required. 883 Physical volumes in pool exceed the limit of 15 Cause The updater is configured to a virtual SMF disk that consists of more than 15 physical disks. This configuration is not supported by the RDF product.
887 Process trapped. Signal sig-num sig-num is the signal number associated with the trap. Cause The process reporting the event experienced an internal error and has trapped. The message indicates the signal number associated with the trap. Effect The process abends. Recovery This is an internal error. Preserve the saveabend file created and report the incident to your service provider. 888 MAT position for File Recovery: SNO num RBA num Cause A successful takeover has completed.
891 First network transaction to be undone: %identifier identifier is the transaction identifier. Cause This is the first transaction that requires network undo with respect to business consistency across all backup nodes. All transactions that committed after this transaction are undone on this node except those transactions that can be safely kept because they actually committed before this transaction on one or more different primary nodes in the RDF network.
Cause The auxiliary receiver has detected information about an SQL SHARED ACCESS DDL operation associated with the specified SNO and RBA in the Master Audit Trail (MAT) on your primary system. Effect The auxiliary receiver coordinates stopping its updaters at the correct location. Recovery This is an informational message. When all updaters on all trails have shut down for the SQL NSA operation, you can execute the same DDL operation on your backup system.
Recovery If this happens during a takeover operation, reissue the TAKEOVER command. When the updater restarts the table will automatically be resized to accommodate the required number of transactions. If this happens in a stop-update-to-time operation, restart RDF and issue a new STOP UPDATE, TIMESTAMP command at a time when there are fewer transactions active.
Effect If this message comes from the master receiver, then normal RDF TAKEOVER processing is ready to proceed. If it comes from an auxiliary receiver, then normal RDF TAKEOVER processing does not start until the master receiver has finished ZLT processing. Recovery This is an informational message; no recovery is required. 904 Auxiliary receiver is catching up Cause The master receiver has found a TMF shutdown record.
907 Backup process creation error nnn nnn, file filename nnn nnn are the error number and error detail returned by the PROCESS_CREATE_ system procedure. filename is the name of the program file that was to be executed. Cause The primary process of an RDF NonStop process pair encountered an error while attempting to create its backup process.
Cause The purger logs this event whenever all updaters have stopped following a STOP UPDATE command. Effect The updater processes are stopped. Recovery This is an informational message; no recovery is required. 911 Updaters stopped before STOP RDF, DRAIN has completed Cause The purger has detected that all the updaters have stopped, but at least one updater stopped prematurely and did not drain all audit. Effect The STOP RDF, DRAIN is not complete.
915 Drain operation complete but a primary volume is down Cause A STOP RDF, DRAIN or STOP RDF, REVERSE command has completed but RDF has detected that a volume on the primary node is down. Effect Any transactions that touched the affected volume that were active when the volume went down are unresolved (on both the primary and backup systems). If this event is the result of a STOP RDF, REVERSE, the REVERSE trigger is not executed.
Recovery Restart RDF and the STOP TMF record will be processed as normal. Once RDF has stopped as a result of the STOP TMF record, RDF can be restarted and a new STOP RDF, DRAIN (or REVERSE) command can be issued.
index is the string index at which the mapping string is invalid. filename is the name of the updater mapfile specified in the updater configuration. cause identifies the reason for the mapping string to be invalid. Cause The updater has detected that the specified mapping string is invalid. The position, if included in the event, indicates the string index at which the mapping string is invalid. The event also includes a description of the reason for the string to be invalid.
mapping-string identifies the invalid mapping string. index is the string index at which the $ character is detected. filename is the name of the updater mapfile specified in the updater configuration. Cause The updater has detected the $ character in the specified mapping string. The volume name is not allowed in the mapping string. The position indicates the string index at which the $ character is found. Effect The updater stops and RDF aborts.
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. $ character detected in the mapping string mapping-string in the MAPFILE filename mapping-string is the erroneous mapping string specified in the mapfile. filename is the name of the updater mapfile specified in the updater configuration.
ALTER of this element cannot be performed with RDF up Cause An ALTER command was issued for a non-runtime ALTER option. Effect The command fails. Recovery Either shut down RDF and reenter the ALTER command, or select another command to enter. ALTER of this element cannot be performed with updaters running Cause An ALTER command was issued for a non-runtime ALTER option. Effect The command fails. Recovery Stop updating by entering the STOP UPDATE command through RDFCOM, and then reenter the ALTER command.
Recovery To determine which updaters terminated prematurely, examine the EMS event log for error number 726. Then, reissue the TAKEOVER command. A required attribute for network master is missing Cause You must specify 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 Add one or more network records to the configuration describing the non network master subsystem(s). Audit is missing. Contact your HP analyst. Cause The COPYAUDIT command could not find audit that should exist in the local image trail. Effect The COPYAUDIT command aborts. Recovery There might be no recovery for this problem. To verify that required audit is missing from your local image trail, contact your local HP analyst.
Cause The RDF configuration file is invalid. Effect The RDF configuration record was not added. Recovery Enter a SET RDF command, using the BACKUPSYSTEM parameter to identify the backup system. Then, enter an ADD RDF command to add this system to the configuration. BACKUPSYSTEM \node is Unavailable node is the name of the backup node that was unavailable. Cause Either the START RDF command failed because the backup node was unavailable, or the RDF configuration file is invalid.
Cause The RDF configuration file is invalid. Effect The VALIDATE CONFIGURATION or START RDF command that checked the configuration file fails. Recovery Check and correct the configuration file. Then reenter the VALIDATE CONFIGURATION or START RDF command. Couldn't create or clear the BACKUPSYSTEM CONTEXT (error#) error# is the file-system error number that identifies the specific error.
Couldn't OPEN the started process: error# error# is the error number that identifies the specific error. Cause An open error occurred during START RDF or STOP RDF command processing. Effect The START RDF or STOP RDF operation is aborted. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting process errors, see the Guardian Procedure Errors and Messages Manual.
Creation error error# on IMAGETRAIL volume-name error# is the file-system error number that identifies the specific error. volume-name is the image trail volume on which the error occurred. Cause During execution of a START RDF command or a VALIDATE CONFIGURATION command, RDFCOM determined that sufficient disk storage for image files did not exist in each secondary image trail for at least one additional image file.
placed on TMF data volumes configured to the Master Audit Trail. If your data must remain on TMF data volumes configured to auxiliary audit trails, then you must reconfigure your RDF subsystem without lockstep protection. You must rethink what data you want protected and whether or not it needs lockstep protection. You might have to configure two separate RDF subsystems, protecting lockstep data with one subsystem, and protecting the data associated with auxiliary audit trails with the other RDF subsystem.
Cause The TMP returned the specified file-system error number when attempting to unpin a TMF audit trail file. Effect The UNPINAUDIT command is ignored. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. Take appropriate corrective action, and then reissue the UNPINAUDIT command.
Effect The RDFCOM command being executed fails. Recovery Correct the underlying problem with the SMF pool and reissue the RDFCOM command. Error error# on allocation of extents for imagefile error# is the file-system error number that identifies the specific error. Cause The COPYAUDIT command encountered the specified error while attempting to allocate extents for a new image file on the local image trail. Effect The COPYAUDIT command aborts.
Messages Manual. Correct the error and reenter the INITIALIZE RDF command. If the problem persists, contact your system manager. Error error# on filename while cleaning the control subvolume on the remote system. error# is the file-system error number that identifies the specific error. filename is the name of the remote control subvolume file associated with the error. Cause The INITIALIZE RDF command encountered the specified error while attempting to purge the remote control subvolume files.
Cause The COPYAUDIT command encountered the specified error while attempting to perform a SET MODE operation to set the ownership for a new image file on the local image trail. Effect The COPYAUDIT command aborts. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. Take appropriate corrective action, and then reissue the COPYAUDIT command.
mapping-string is the erroneous mapping string specified in the mapfile. filename is the name of the updater mapfile specified in the updater configuration. Cause RDFCOM found that the mapping string specified in the updater mapfile did not contain the keyword MAP when an ADD VOLUME, ALTER VOLUME, START RDF, START UPDATE, or VALIDATE CONFIGURATION command was being executed. Effect The command fails. Recovery Add the keyword MAP in the mapping string, then reenter the command.
Recovery Check the control subvolume name and make sure that you are spelling it correctly. Then reenter the command, including the proper control subvolume name or specifying a different control subvolume. Expecting: RDF, MONITOR, EXTRACTOR, RECEIVER, VOLUME Cause RDF did not understand the command. Effect The command fails. Recovery Check the syntax rules for the command you entered. Perhaps you misspelled a keyword parameter or misplaced a delimiter. Expecting 'Yes' or 'No' response.
Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect The START RDF or TAKEOVER operation is aborted. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting process errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error. Otherwise, see your system manager.
Filename is not licensed. Filename is the name of an RDF program file that is used to create an RDF subsystem process. Cause When a START RDF command or a VALIDATE CONFIGURATION command is executed, RDFCOM determined that the program file used for creating a RDF subsystem process is not licensed. Effect The command fails. Recovery License the program file. Then, reenter the START RDF or VALIDATE command. File is not an edit file filename.
Effect Validation fails. Recovery Before you can validate your local RDF subsystem, you must configure all RDF subsystems in your network. If INITIALIZE command is specified in an IN file the pound (#) character should be used with bang (!) option. Cause INITIALIZE RDF command was issued using an IN file to RDFCOM with "#" operator but without the "!" option. Effect The command fails. Recovery When issuing the INITIALIZE RDF using an IN file to RDFCOM with "#" operator, specify "!" operator also.
Recovery There might be no recovery for this problem. You must perform the database synchronization without the help of RDFCOM. IMAGETRAIL for IMAGEVOLUME vol-name does not exist vol-name is the image trail volume for which the image trail does not exist. Cause You tried to add an updater, but have not yet added an image trail for the updater’s volume. Effect The ADD command fails. Recovery Add the image trail. Then add the updater.
Cause You tried to add a secondary image trail on the volume volume-name, but an image trail has already been added for this volume. Effect The command fails. Recovery Select a different volume for the secondary image trail. IMAGETRAIL volume-name is not used by any updater volume-name is the name of the image trail. Cause While validating your configuration, RDFCOM determined that the image trail on the volume volume-name is not referenced by any updater processes. Effect The validation operation aborts.
Recovery Delete this image trail volume and all updaters that refer to it. IMAGEVOLUME volume-name is not a legal volume name volume-name is the name of the volume. Cause The SET VOLUME IMAGEVOLUME command specified an invalid volume name. Effect The command fails. Recovery Reenter the command, using a correct volume name. Inconsistent network options are not allowed Cause You have attempted to add the RDF configuration record with the RDF NetworkMaster attribute on but the Network attribute off.
Cause You tried to initialize RDF with the SYNCHDBTIME option, but RDF/IMP or IMPX is not installed. Effect The INITIALIZE RDF command fails. Recovery If you want to perform online database synchronization, RDF/IMP or IMPX must be installed on both the primary and backup systems. INITIALIZE RDF aborted Cause This message follows a previous error message that indicates why the INITIALIZE RDF command failed. Effect RDF is not initialized.
Cause When a VALIDATE CONFIGURATION command is executed, RDFCOM determined that a user specified spooler location for report generation is not a spooler location. Effect The command fails. Recovery Reenter the VALIDATE command with a valid filename or spooler location. Invalid TMF shutdown timestamp Cause You entered an INITIALIZE RDF timestamp command, but specified the timestamp (or one or more of its components) incorrectly. Effect RDF is not initialized. Recovery Examine the specified timestamp.
Recovery See the Operator Messages Manual for a description of the error code. For additional information about understanding and correcting process errors, see the Guardian Procedure Errors and Messages Manual. Correct the error and reenter the START RDF or TAKEOVER command. Local image file filename is missing filename is the name of the image trail file. Cause The COPYAUDIT command could not find the specific image file on the local image trail, although this file should exist on disk.
Recovery See the Guardian Procedure Errors and Messages Manual for a description and recovery actions for the file-system error. Correct the error indicated by error#, then, reenter the command. Mapping string mapping-string is invalid in the MAPFILE filename The subvolume subvolume-name is invalid. mapping-string is the erroneous mapping string specified in the MAPFILE. filename is the name of the updater MAPFILE specified in the updater configuration.
Effect The ADD EXTRACTOR command fails. Recovery Review and revise your RDF configuration. Maximum number of image trails already added Cause You have already added the maximum number of secondary image trails (255), and cannot add more. Effect The command fails. Recovery No recovery action is possible; your RDF subsystem can only support 256 secondary image trails. Missing network master NETWORK record Cause No network record exists that corresponds to the network master subsystem.
Recovery If you need to run in an RDF network, you need to obtain the RDF/IMPX license and product. NETWORK record can only be added into a networked subsystem Cause An ADD NETWORK command was entered but the RDF NETWORK parameter is set OFF. Effect The ADD NETWORK command is rejected. Recovery Reconfigure RDF to have the RDF NETWORK parameter set ON. Network record not found Cause The current RDF subsystem is configured in an RDF network, but a network record has not been added. Effect Validation fails.
Cause You added a receiver with the specified ATINDEX, but there is no extractor with that value. Effect The validation fails. Recovery Add an extractor with the same ATINDEX value or delete the particular receiver. No RECEIVER is configured for ATINDEX atindex Cause You added an extractor with the specified ATINDEX, but there is no receiver with that value. Effect The validation fails. Recovery Add a receiver with the same ATINDEX value or delete the particular extractor.
Effect The validation fails. Recovery Alter the configuration to include the monitor. No PCB available Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect The command fails. Recovery Check system resource utilization. When resources become available, reenter the command. No RECEIVER is Configured Cause The RDF configuration file is invalid. Effect The configuration validation fails.
Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the COPYAUDIT command. Otherwise, see your system manager. Only one Network record is allowed for a non-network master Cause Your current RDF configuration does not have the NetworkMaster attribute set and you have tried to add more than one network record.
Effect The command fails. Recovery See the Guardian Procedure Errors and Messages Manual for a description of the recovery actions for the file-system error. Correct the error indicated by error#, then reenter the command. Open error error# on report file filename. error# is the file-system error number that identifies the specific error. filename is the name of the file you specified for generating the report.
Operation must be performed on the PRIMARYSYSTEM \primary or BACKUPSYSTEM \backup primary is the name of the primary node that can perform the operation. backup is the name of the backup node that can perform the operation. Cause The command was issued at a third system, which is not allowed. Effect The command fails. Recovery Enter another command, or reenter this command at the specific primary or backup node reflected by this message.
Recovery You must reconfigure your network master and possibly your local configuration. Position error error# on file remote-config-file error# is the file-system error number that identifies the specific error. remote-config-file is the name of the remote configuration file. Cause The COPYAUDIT command encountered the specified error while attempting to position into the remote configuration file. Effect The COPYAUDIT command aborts.
error# is the file-system error number that identifies the specific error. Cause The COPYAUDIT command encountered the specified error while attempting to position into a remote image file on the remote image trail. Effect The COPYAUDIT command aborts. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual.
error# is the error number that identifies the specific error. Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect The START RDF or TAKEOVER operation is aborted. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting process errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error.
Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect The START RDF or TAKEOVER operation is aborted. Recovery Change the library filename. Program File Error: error# on progfile error# is the error number that identifies the specific error. progfile is the name of the program file on which the error was encountered. Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect The START RDF or TAKEOVER operation is aborted.
RDF LOGFILE filename NOT a legal filename on system \node filename is the name of the nonexistent EMS collector (RDF log file). node is the name of the system where the collector name is invalid. Cause The RDF configuration file is invalid: a nonexistent EMS collector was specified. Effect The ADD RDF command fails. Recovery Specify a valid EMS collector name in a SET RDF command, and then reenter the ADD RDF command.
Recovery Alter the configuration to include all RDF global parameters. RDF Shutdown in progress, please wait... Cause RDF is shutting down. Effect The shutdown operation continues. Recovery This is an informational message; no recovery is required. RDF START Failure, Scan LOGFILE for reason Cause A START RDF command failed. RDF writes a description of the problem in the LOGFILE. Effect The START RDF command fails. Recovery Check the EMS event log for the message covering this error.
Effect The attempted command is aborted. Recovery Contact the Global Mission Critical Solution Center (GMCSC) or your service provider. RDFCOM is asking the TMP to restore the file. If the file was previously dumped to tape, watch for the TMP to tell you to mount the appropriate tape. Cause In response to a prompt, you requested RDFCOM to trigger restoration of an audit trail file.
Effect The ADD command fails. Recovery Issue a RESET RECEIVER command, and then reconfigure the particular receiver without specifying an RDFVOLUME. Read error error# on file remote-config-file error# is the file-system error number that identifies the specific error. remote-config-file is the name of the remote configuration file. Cause The COPYAUDIT command encountered the specified error while attempting to read the remote configuration file. Effect The COPYAUDIT command aborts.
error# is a file-system error number that indicates lack of storage space on disk. Cause During execution of a START RDF command, RDFCOM determined that sufficient disk storage for image files did not exist. As one of its validation checks during START RDF processing, RDFCOM tries to create a temporary image file on the receiver’s RDFVOLUME and then to allocate all 16 extents.
Recovery Specify a valid disk volume. RECEIVER RDFVOLUME volume-name does NOT exist volume-name is the name of the nonexistent RDFVOLUME file. Cause The RDF configuration file is invalid. Effect The validation of the receiver fails. Recovery Specify a valid disk volume. RECEIVER Record does not exist Cause You tried to add a secondary image trail before adding the receiver’s configuration record. Effect The command fails. Recovery Add the receiver’s record. Then, add the secondary image trail.
Recovery Determine why the receiver record for the subsystem cannot be obtained. RECEIVER Record with ATINDEX atindex does not exist. Cause You tried to add an imagetrail with the specified ATINDEX, but there is no receiver with that value. Effect The ADD command fails. Recovery You must add the corresponding receiver process before adding an imagetrail with the same ATINDEX value.
Effect The command fails. Recovery Remove the reserved subvolume name in the mapping string, then reenter the command. Restore failed with error error# Search is stopped. error# is the file-system error number that identifies the specific error. Cause Restoration of an audit trail file has failed for the reason indicated by error#. Effect RDFCOM immediately terminates its search for a TMF shutdown timestamp and then its attempt to initialize RDF.
Effect The shutdown operation is aborted. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error. Otherwise, see your system manager. SHUTDOWN Failure: error# on VOLUME volume error# is the error number that identifies the specific error. volume is the name of an RDF data volume.
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. 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. timestamp is the shutdown timestamp to which the initialization was requested.
Effect The start operation continues for RDF. Recovery This is an informational message; no recovery is required. STATUS RDF (\primary-> \backup) is NOT running primary is the name of the primary node in the RDF configuration. backup is the name of the backup node in the RDF configuration. Cause A STATUS RDF command was issued while RDF was not running. Effect The command fails. Recovery Enter another command, or wait until RDF is started and then reenter the STATUS RDF command.
Cause You entered a STOP UPDATE command, but the monitor could not send stop messages to all updater processes and has logged RDF error 841 to the EMS event log. Effect Some updaters might have shut down, but others never received the stop message and are still running. The receiver and monitor cannot now identify these updaters, and you cannot stop them with another STOP UPDATE command or a STOP RDF command.
Effect The RDFCOM INITIALIZE RDF command continues. Recovery This is an informational message; no recovery is required. Synch timestamp is synchdbtime synchdbtime is a SYNCHDBTIME timestamp specified previously by an operator in an RDFCOM INITIALIZE RDF command. Cause In conjunction with a complete database synchronization, you are attempting to initialize RDF to a timestamp that is earlier than the current time.
Recovery Either use the OPEN command to open an RDF CONFIG file in an existing RDF control subvolume, or initialize a new RDF configuration with the INITIALIZE RDF command. The control subvolume \sys.$SYSTEM.subvol is not empty. The files on the control subvolume must be purged. Please note, these files might belong to another RDF configuration. sys is the name of the primary system. subvol is the name of the local RDF control subvolume.
Cause RDFCOM could not find the updater mapfile when an ADD VOLUME, ALTER VOLUME, START RDF, START UPDATE, or VALIDATE CONFIGURATION command was being executed. Effect The command fails. Recovery Provide an existing mapfile and reenter the command. The MAPFILE filename should be an edit file filename is the name of the updater mapfile specified in the updater configuration.
seq-num is the sequence number of the MAT file. Cause While searching for a TMF shutdown timestamp to use to initialize RDF, RDFCOM found that the audit trail file with the specified sequence number is not currently available. If you respond to the prompt with YES or Y, RDFCOM directs the TMP to begin restoring this file. NOTE: If the file was dumped to tape, you must wait for the TMP to prompt you to mount the tape. This mount request is logged in the EMS log.
Effect The COPYAUDITcommand aborts. Recovery Correct the REMOTESYS remote-sys and REMOTECONTROLSUBVOL rcvs parameters and reissue the COPYAUDIT command. RDFNET must be a named process Cause You must specify a process name for the RDFNET process before issuing an ADD command. Effect The start command fails. Recovery You must reconfigure RDF with a named RDFNET process. "The remote control subvolume\bksys.$SYSTEM.subvol is not empty. The files on the remote control subvolume must be purged.
Recovery Reissue the STOP UPDATE, TIMESTAMP command, specifying a timestamp that is at least five minutes ahead of the current time. The STOP SYNCH command is aborted because it has been issued previously. Cause You are attempting to execute an RDFCOM STOP SYNCH command, but the command has already been issued previously. Effect The RDFCOM STOP SYNCH command aborts. Recovery You can only execute the STOP SYNCH command if the RDF product is currently involved in online database synchronization.
Recovery Reissue the command, specifying a timestamp year that is 1997 or greater. This aux EXTRACTOR Record already exists. Cause You tried to add an EXTRACTOR with a particular ATINDEX value, but there is already one configured with that value. Effect The ADD command fails. Recovery Review and revise your RDF configuration. This aux RECEIVER Record already exists. Cause You tried to add an RECEIVER with a particular ATINDEX value, but there is already one configured with that value.
Effect The requested RDFCOM operation fails. Recovery Configure and start TMF, and request the RDFCOM operation again. TMF is not running. Cause While either attempting to validate the RDF configuration or to start RDF, RDFCOM discovered that TMF is not running. Effect The command fails. Recovery Start TMF. Then validate your configuration and start RDF. TMF is not started yet. Cause TMF has not been started. Effect The requested RDFCOM operation fails.
TMF STOP in progress. Cause A TMF stop operation is in progress. Effect TMF stops, and RDF automatically stops thereafter. Recovery This is an informational message; no recovery is required. To issue this command, the RTD time of the extractor must be 0:00. Have you confirmed that the RTD is 0:00? Cause You are attempting to execute an RDFCOM STOP SYNCH command. To ensure that the extractor does not miss any audit record, the extractor RTD must be 0:00 before executing this command.
Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect The NEWPROCESS procedure fails. Recovery Make sufficient space available on the swap volume for the requested operation. Unable to communicate with CPU cpu cpu is the CPU that is not responding. Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect The NEWPROCESS procedure fails. Recovery Check the status of the CPU, or enter SET and ALTER commands to direct the process to run on a different CPU.
Effect The command fails. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. Manually purge any files on the image file subvolume, and then reissue the START RDF command. Unable to purge remaining image files; error error# error# is the file-system error number that identifies the specific error.
UPDATE is already off Cause A STOP UPDATE command was issued when updating is disabled. Effect The command fails. Recovery This is an informational message; no recovery is required. UPDATE is already on Cause A START UPDATE command was issued when updating is enabled. Effect The command fails. Recovery This is an informational message; no recovery is required. UPDATE request could not be performed Cause RDFCOM could not execute a START UPDATE or STOP UPDATE command. Effect The command fails.
Cause An ADD VOLUME command was issued when the configuration file already contained an updater record for the volume. Effect The RDF command fails. Recovery No recovery is required if you want to use the existing updater process as it is configured. If you want to change any of the updater’s configuration options, however, enter an ALTER VOLUME command that specifies those changes.
Cause You tried to delete an image trail that is still being used by an updater. Effect The command fails. Recovery Delete the updater, and then delete the image trail. VOLUME vol-name does not match imagetrail ATINDEX atindex Cause You added an updater with the specified ATINDEX, but the IMAGEVOLUME configured for the updater does not have that value. Effect The validation fails. Recovery Alter the particular updater’s ATINDEX value to match the appropriate audit trail number or delete the updater.
Cause The user attempted to SET or ALTER the RDF BACKUPSWAP parameter. Effect This parameter no longer has any effect. The KMSF subsystem controls the placement of the RDF processes’ swap files. Recovery This is an informational message; no recovery is required. *** Warning *** FASTUPDATEMODE is already OFF. Cause You have tried to turn FASTUPDATEMODE OFF for a Receiver when it was already OFF. Effect The command is ignored. Recovery This is an informational message; no recovery is required.
WARNING - PRIMARYSWAP parameter has no effect, KMSF swap volume takes precedence Cause The user attempted to SET or ALTER the RDF PRIMARYSWAP parameter. Effect This parameter no longer has any effect. The KMSF subsystem controls the placement of the RDF processes’ swap files. Recovery This is an informational message; no recovery is required. * * * WARNING * * * RDF will start at the first record in the TMF master audit trail beyond the specified shutdown timestamp.
Cause REPLICATEPURGE is turned OFF but INCLUDEPURGE or EXCLUDEPURGE lists have been added for a volume. Effect The INCLUDEPURGE or EXCLUDEPURGE lists will be ignored for the volume. Recovery SET RDF REPLICATEPURGE to ON before starting RDF. *** Warning *** Updater Open Mode has been specified the same value as it was before using the ALTER RDF UPDATEROPEN command. Cause The ALTER RDF UPDATEROPEN command has been specified with the same mode which was present prior to issuing the command.
Cause The COPYAUDIT command encountered the specified error while attempting to write data to the local ZFILEINC file. Effect The COPYAUDIT command aborts. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the underlying error and reenter the COPYAUDIT command. Otherwise, contact your service provider.
Effect If you respond YES or Y, RDF executes the command. If you respond NO or N, the command terminates. Recovery This is an informational message; no recovery is required. You are about to unpin a file that the extractor needs. Are you sure you want to proceed? Cause You have asked RDFCOM to unpin a file that is currently needed by the extractor. If you respond “yes,” the file is unpinned and TMF can rename it. If the file is renamed, RDF cannot be restarted until you restore the file.
You cannot alter MAPFILE on the backup system if the primary system is available Cause During execution of an ALTER VOLUME command on the backup system, RDFCOM determined that the primary system is accessible. Effect The command fails. Recovery Reenter the command on the primary system. You cannot alter MAPLOG on the backup system if the primary system is available Cause During execution of an ALTER VOLUME command on the backup system, RDFCOM determined that the primary system is accessible.
Cause You tried to add an auxiliary receiver before adding the master receiver. Effect The ADD command fails. Recovery You must add the master receiver first. You must specify the year with four digits Cause You specified the year in a timestamp with less than four digits. Effect The command involving the timestamp fails. Recovery Reissue the command, specifying a four-digit year in the timestamp.
Effect The command fails. Recovery See the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error. Otherwise, see your system manager. File error: error# trying to read RDFlog file error# is the file-system error number that identifies the specific error.
Invalid request Cause The request was not a valid RDFSCAN command. Effect The command fails. Recovery Enter another RDFSCAN command.
D Operational Limits Table 17 Operational Limits for RDF/IMP, IMPX, and ZLT Limit Description Maximum Value Number of volumes being protected 255 Number of volumes in an SMF pool on backup system 15 Number of auxiliary image trails 255 Number of files per updater 3000 Number of RDF configurations with the same primary system 37 Number of systems that can contribute audit to a primary system 255 Maximum number of image trail file primary and secondary extents 65,500 Maximum number of primary
E Using ASAP ASAP (Availability Statistics and Performance) allows many subsystem entities to be monitored across a network of NonStop servers. The status and statistics for the entities are collected on a single system, and are then monitored either through the ASAP command interface or through the ASAP graphical user interface (GUI) PC client.
Figure 16 The RDF/ASAP Environment Installation The RDF SGP is packaged with the RDF/IMP and IMPX products and, by default, is installed on $SYSTEM.RDF. You might, however, place this object file wherever you want. If you install the SGP object file somewhere other than $SYSTEM.RDF, you must ensure that the ASAP configuration points to the correct location (by way of the SET RDF command within the ASAP command interface). See the ASAP Server Manual for details about the SET RDF command.
This command uses DOME as the CSV. To use a control subvolume with a suffix, say E, one should use the command: MONITOR RDF DOMEE->TANDA where, DOMEE is the control subvolume and TANDA is the RDF Backup System without '\'. Adding and Removing RDF Environments The RDF SGP performs the auto detection and processing of the RDF environments added through the MONITOR command when the process starts.
Table 18 RDF Metrics Reported by ASAP (continued) Information Passed to ASAP Monitor Extractor Receiver Imagetrail Purger RDFNET Updater File Sequence Number X X X — — — X Relative Byte — Address X — — — — X RTD Time X X X — — — X Primary CPU X X X — X X1 X Backup CPU X X X — X X1 X X 1 X Priority 1 2 X X X — X Only in an RDF Network environment Only reported by the master receiver where the master image trail (MIT) volume is reported RDF Metrics Report
Index * wildcard character, 257 900, File code, 57 ? wildcard character, 257 ] prompt, 91 views, 58 volume names, 53 BACKUPSWAP parameter, 217 BACKUPSYSTEM network attribute, 280 BACKUPSYSTEM parameter, 201 Bracket prompt (]), 91 A C Abbreviations, 192, 331 ADD command, 182, 330 ADD EXTRACTOR command, 81, 85 ADD MONITOR command, 84 ADD RECEIVER command, 85, 87 ALTER command, 184, 330 ALTER command, FUP, 67 Altering TMF configuration, 71 ASAP, Using with RDF, 51, 480 Asterisk wildcard character, 257 AT c
VALIDATE CONFIGURATION, 247, 337 RDFSCAN AT, 251, 338 DISPLAY, 251 EXIT, 252, 338 FILE, 253, 338 HELP, 254, 338 LIST, 254, 338 LOG, 255, 338 MATCH, 256, 338 NOLOG, 256, 257, 338 SCAN, 258, 339 RDFSCAN commands DISPLAY, 338 STATUS RDF, 104 Communications estimating required resources, 53 RDF requirements, 52, 54 Communications line failure, 118 Comparing SQL/MX tables, 319 CONFIG file description, 343 Configuration backup system, 52 command file, creating for RDF, 89 extractor process, 81, 85 monitor process
purge operations, 59 Error messages, file system, 347 Error recovery create operation, 115 modify operation, 114 open operation, 114 RDF error 700, modify operation, 114 RDF error 705, open operation, 114 RDF error 739, create operation, 115 Event log, scanning messages in EMS, 34, 109 Exception files description, 344 examining, 343 records, 34 EXCLUDE clauses, 266 EXIT command, 189, 252, 331, 338 Expand estimating required resources, 53 multi-CPU paths (superpaths), 278 EXPAND line failure, 118 Extractor p
RDF, 72 TMF, 71 INITTIME parameter, 74, 202 Installing the RDF subsystem, 68 K Keywords, 95 L Label modifications, file, 59 Licensed programs, 69 Line failure, 118 LIST command, 254, 338 LOCATION option, 317 Lockstep gateway messages, 297 Lockstep operation, 50 LOG command, 255, 338 Log device, messages sent to, 346 Log file, 250 $0, 347 description, 33 example, 110, 346 messages in, 109 scanning messages in, 34 specifying in RDFSCAN, 253, 338 Log, EMS event, 109 LOGFILE parameter, 217 M Managing the RDF
OBEY command files, 95, 341 backup system, 64, 67 synchronizing databases with, 64 OBEYFORM option, 195 of INFO command, 89 OBEYVOL command, 206 ODBC catalog changes, 151 Offline synchronization for a single partition, 314 Online database synchronization, 158 phases of, 173 Online help RDFCOM, 99 RDFSCAN, 103 Online initialization, 73 OPEN command, 206, 332 Open operation error recovery, 114 file-system errors, 114 RDF errors, 114 Operating system RDF requirements, 54 security, 69 Operating the RDF subsyste
introduction to, 27 licensed programs, 69 log device for messages, 346 log file, 33, 250 log file example, 346 managing, 91 messages, 346, 347 messages, scanning, 34, 109 network transactions, 279 NonStop process pairs, 36 operating, 91 operations, 37 parameters, 217 BACKUPSWAP, 217 BACKUPSYSTEM, 201 CPUS, 210, 212, 213, 214, 215, 220, 221, 223, 225, 333, 334 EXTENTS, 215, 221 image trail, 81 IMAGETRAIL, 188 IMAGEVOLUME, 225 LOGFILE, 217 monitor process, 84 PRIMARYSWAP, 217 PRIORITY, 210, 212, 213, 214, 215
monitor object file, 68 security requirements, 70 RDFNETO, security requirements, 70 RDFRCVO licensed program, 69 receiver object file, 68 security requirements, 70, 71 RDFSCAN description, 250 description of use, 34, 109 ending a session, 102 help text file, 68 messages, 476 object code file, 68 online help, 103 running, 101 security requirements, 71 starting a session, 101 wildcard characters in match patterns, 257 RDFSCAN commands AT, 251, 338 DISPLAY, 251, 338 EXIT, 252, 338 FILE, 253, 338 HELP, 254, 33
SQL/MX name mapping, 316 SQL/MX offline synchronization for a single partition, 314 SQL/MX tables comparing, 319 restoring, 317 START RDF command, 90, 231, 336 START TMF command, TMFCOM, 89 START TRANSACTION command, TMFCOM, 67, 71 START UPDATE command, 90, 232, 336 Starting the RDF subsystem, 89 Starting the TMF subsystem, 89 STATUS RDF command, 104, 233, 336 STOP RDF command, 239, 337 STOP SYNCH command, 241, 337 STOP UPDATE command, 141, 241, 337 stop-update-to-time, 141, 242, 399 Stopping the backup sys
SET VOLUME example, 227 setting option values, 225 SHOW VOLUME example, 230 partitioned files, auditing, 43 RDF errors, 113 restart point, 43 restart points, error recovery, 113 Updater, failure, 119 UPDATERDELAY parameter, 217 UPDATEVOLUME parameter, 225 User interfaces, RDF subsystem, 33 V VALIDATE CONFIGURATION command, 247, 337 Views, NonStop SQL/MP, 58, 64 Volume audited on backup system, 63 configuration, 53 failure, TMF, 120 limit, 53 mapping, 53 mapping primary to backup, 63 names, 180 names, diffe
