HP NonStop RDF J-series RVUs Management Manual page 380

Cause The purger has detected that all the updaters have shut down following a successful
stop-update-to-time operation.
Effect
The database is now in a consistent state.
Recovery
758
Process abending
Cause The indicated process is abending.
Effect A SAVEABEND file is created, a stack trace is logged, and the process (and its backup
process, if any) abends. RDF stops.
Recovery
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. If the record is associated with an Enscribe create
operation, the specific partition of the file is not created on the backup system. Therefore, if
the updater subsequently encounters another audit record associated with that file, the updater
pauses its processing until that file is created.
Alternatively, if the record was associated with a PURGEDATA or increase to MAXEXTENTS,
the operation is not replicated on the backup system.
Recovery
file on the backup system. If the record was associated with a PURGEDATA or increase to
MAXEXTENTS, you must issue the STOP UPDATE command and then perform the operation
manually on the backup system.
760
Image trail file purged filename
filename
is the name of an image trail file.
Cause The purger has determined that the specified image file is no longer needed and has
purged it.
Effect
The specified file is purged.
Recovery
761
Backup stopped
Cause The backup process of a process pair has been stopped. This probably was the result
of an operator inadvertently issuing a STOP command from TACL.
Effect
A new backup will be created.
Recovery
762
Context file is old; must INITIALIZE RDF
Cause An RDF process has determined that the existing context file belongs to an older
version of RDF.
380 Messages
This is an informational message; no recovery is required.
Restart the RDF product and report the error to your service provider.
If the record was associated with an Enscribe create, you must manually create the
This is an informational message; no recovery is required.
This is an informational message; no recovery is required.