RDF/IMP and IMPX System Management Manual (RDF 1.4+)

Operating and Monitoring RDF
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
4-21
Displaying Current Configuration Parameters and
Operating Statistics
(*****), the updater has experienced a critical error. If the updater is doing an undo
pass, the word undo appears in the Error column. If RDFCOM cannot reach a
particular process, the Error column for that process contains the applicable file
system error number.
The occurrence of a critical error could mean that the backup database is no
longer synchronized with the primary database because of data loss. If asterisks
appear in the Error column for any RDF process, you should examine the
messages in the RDF log file or on the RDF log device to determine what is
happening and what corrective action to take.
Except for updaters, asterisks in the Error column continue to appear in every
STATUS RDF display until the error condition has been corrected.
For updaters, the asterisks disappear when the error corrected is corrected and
updating is restarted after execution of any of the following commands:
STOP UPDATE
STOP RDF
STOP TMF
Note that although the occurrence of a critical error might mean that the primary
and backup databases are no longer synchronized with one another, that is not
always the case. If, for example, the primary CPU of the disk process goes down,
all updater processes affected by that error condition report a file system error and
then attempt to restart. If the error does not occur again when the affected updater
processes restart, the databases are probably still synchronized with one another.
In that case, the asterisks are cleared from subsequent STATUS RDF displays.
For more information on critical errors, you can scan the EMS collectors on the
primary and backup systems:
The EMS collector on the primary system contains log messages for the
extractor and monitor processes.
The EMS collector on the backup system contains log messages for the
receiver, purger, and all updater processes.
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.
When the BREAK key is pressed while the STATUS RDF command is executing with
the PERIOD option (which requests repeated displays at a specified interval), the
break takes effect within one second rather than waiting until the end of the current
interval.