Critical Operations, Special Situations, And Error Conditions; Recovering From File System Errors - HP NonStop RDF J-series RVUs Management Manual

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.
This chapter, which is directed to both system managers and operators, discusses the following
topics:
• "Recovering From File System Errors" (page 121)
• "Handling Disk Space Problems" (page 124)
• "Exceeding the Maximum Number of Concurrent File Opens" (page 125)
• "Responding to Operational Failures" (page 125)
• "Stopping RDF" (page 132)
• "Restarting RDF" (page 136)
• "Carrying Out a Planned Switchover" (page 136)
• "Takeover Operations" (page 139)
• "Reading the Backup Database (BROWSE versus STABLE Access)" (page 149)
• "Access to Backup Databases with Stable Access" (page 150)
• "RDF and NonStop SQL DDL Operations" (page 151)
• "RDF and NonStop SQL/MX Operations" (page 153)
• "Backing Up Image Trail Files" (page 153)
• "TMF and Online Dumps on the Backup System" (page 154)
• "Doing FUP RELOAD Operations With Updaters Running" (page 155)
• "Exception File Optimization" (page 155)
• "Switching Disks on Updater UPDATEVOLUMES" (page 155)
• "Online Remirroring of Updater SUBVOLUMES" (page 156)

Recovering From File System Errors

All RDF processes can encounter file system error conditions. If it is RDFCOM, it reports an error
message that includes the file system error in the RDFCOM Outfile. For any other RDF process
(the monitor, the extractor, the receiver, the purger, the updater, or RDFNET), an RDF event is
generated in the EMS event log, and this event includes the specific file system error and any
additional information that is available. Of particular importance are RDF event messages 700,
705, and 739. As an example, file-system error 59 appears in the following RDF event message
705:
10:59 \RDF05
Table 5-1, 5-2, and 5-3 list the most common file system error numbers you might encounter and
each entry provides an appropriate recovery action. For every error condition reported by
RDFCOM as well as for any RDF event, you are also given a detailed explanation of the cause,
effect, and recovery action, and these are all listed in
To analyze a file system error, see the appropriate table in this discussion, reading about any
corrective action specific to RDF. Then, for further information about the error (its cause, effect,
and general recovery procedures), see the file-system information in the Guardian Procedure Error
and Messages Manual.
$WU02 705 File open error 59 on $DATA07.QD004378.RFILE02
Appendix C.
Recovering From File System Errors 121