RDF/IMP, IMPX, and ZLT System Management Manual

HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
5-1
5 Managing RDF
You manage the RDF environment by monitoring various things using RDFCOM
STATUS commands, the EMS log, and the ASAP product.
In managing RDF, you must sometimes react to nonroutine events and conditions that
affect the RDF operating environment, by performing a variety of special tasks and
activities. Although most of this work is not required on a regular basis, the need for it
does arise on occasion. Typically, this work involves using RDFCOM, TMFCOM (the
interactive interface to TMF), SQLCI (the NonStop SQL/MP interactive interface),
TACL (the interactive interface to the HP NonStop Kernel operating system), or FUP.
This section, which is directed to both system managers and operators, discusses the
following tasks:
•
Recovering from file system errors
•
Handling disk space problems
•
Responding to operational failures
•
Stopping RDF
•
Carrying out a planned switchover
•
Initiating takeover operations
•
Reading the backup database
•
Replicating NonStop SQL/MP DDL operations
•
Backing up image trails
•
Making online dumps with updaters running
•
Doing FUP RELOAD operations with updaters running
•
Compressing exception files
Recovering From File System Errors
Errors detected by the operating system’s file system generate error numbers that
appear within RDF messages reported in the EMS event log. Of particular importance
are the file system errors that can cause RDF event messages 700 (modify operation),
705 (open operation), or 739 (create operation). As an example, file system error 59
appears in the following RDF event message 705:
10:59 \RDF05 $WU02 705 File open error 59 on $DATA07.QD004378.RFILE02
Tables 5-1, 5-2, and 5-3 list the file system error numbers and appropriate recovery
actions. In general, when any of these errors occurs, one of the following actions
results: