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

754
Network restored - continuing service
Cause The primary system processes have determined that the communications lines have
been restored. The extractor is now able to communicate with the receiver.
Effect Processing continues from the point at which the network failed.
Recovery This is an informational message; no recovery is required.
755
CHECKMONITOR failure - backup abended
Cause The primary process of a process pair stopped after creating its backup process, but
before completing the backup initialization.
Effect This is a catastrophic error; the process abends, and RDF stops.
Recovery Restart the RDF product and report the error to your service provider.
756
Format-2 audit filtered for filename
filename
is the name of a format-2 database file to which the encountered audit record applies.
Cause The extractor has encountered an audit record associated with the format-2 file
filename and the backup system is not format-2 aware.
Effect The extractor skips the audit record and does not send it to the receiver.
Recovery If you intend to replicate this file you must upgrade the backup node’s operating
system to one that supports format-2 files and resynchronize this file.
757
Updaters stopped, stop-update-to-time operation complete
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 This is an informational message; no recovery is required.
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 Restart the RDF product and report the error to your service provider.
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.
356 Messages