RDF System Management Manual for H-Series RVUs (RDF 1.8)

For information about the causes, effects, and recovery actions for all RDF event messages, see
Appendix C (page 335). When present, file-system error numbers appear in the error# parameter
of these messages.
Table 5-1 lists the file-system error numbers and recovery actions for RDF event 700, which
reports file-modification failures.
Table 5-1 Recovery From File Modification Failures (RDF Event 700)
Recovery ActionFile System Error
Check file integrity. The updater process skips the modify operation. RDF reports error 1
if an updater receives a “record not found” error while attempting to perform the operation.
1
An invalid operation occurred. An error 2 could be caused by a variety of reasons. For
example, error 2 is returned if an application has a data file open for shared write access
and an updater then attempts to open that same file for exclusive write access. In any case,
this is a critical error. You should stop RDF and investigate. If you cannot determine the
cause of the error and remedy the situation, contact your service provider. If an updater
reports an error 2 while attempting to apply an audit record, it skips that record and goes
to the next. In this case, after you correct the error condition, you must reinitialize RDF to
a point earlier than the record that caused the error, and then restart RDF.
2
Check the file integrity. This could mean either loss of data or duplicated audit information.
If data was lost, resynchronize the file. If audit information was duplicated, then no harm
occurred. The updater process skips the modify operation.
10
Check the file integrity. This could mean either loss of data or duplicated audit information.
If data was lost, resynchronize the file. If audit information was duplicated, then no harm
occurred. The updater process skips the modify operation.
11
Check file integrity.16
If the problem persists, alter hardware configuration or perform system tuning.30 through 37
Provide more room for the file or extent by using FUP commands, such as PURGE and
ALTER MAXEXTENTS, or by compressing files. You might need to issue a STOP UPDATE
command.
43 through 45
Repair the device or clear the condition.50 through 58
Check file integrity.59
Repair the device or clear the condition.60 through 66
Check the file integrity. This could mean either loss of data or duplicated audit information.
If data was lost, resynchronize the file. If audit information was duplicated, then no harm
occurred. The updater process skips the modify operation.
71
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. An error 122 or 211 indicates the loss of the primary
CPU of a disk process. This is a normal error from which the RDF process will recover.
122, 211
Repair the device or clear the condition.130 through 139
Check file integrity.157
Repair the device or clear the condition.190
Repair the device or clear the condition.200 through 231
Enable the volume for TMF transaction processing.707
Table 5-2 lists the file-system error numbers and recovery actions for RDF event 705, which
reports file-opening failures.
122 Managing RDF