RDF System Management Manual for H-Series and J-Series RVUs (RDF 1.9)

839
Error - Audit-trail file is missing. File filename
filename
is the name of the audit trail file that could not be found.
Cause The extractor was unable to find the designated audit trail file.
Usually this occurs because TMF has purged the audit trail file while RDF was stopped. When
RDF is running, RDF prevents TMF from purging audit trail files until the extractor has read
them, even if the extractor is running far behind TMF (the extractor has a large RTD value)
and TMF has performed several rollovers. Use the STATUS RDF command to see the extractor’s
current RTD value.
Effect The extractor tries to open the audit trail file indefinitely unless an irrecoverable error
occurs on the file.
Recovery Restore the audit trail file from tape by using SNOOP RESTOREAUDIT.
If copies of the audit trail have not been maintained, then you will have to reinitialize RDF,
and resynchronize the primary and backup databases.
840
Error - Process name is in use, procname
procname
is the name of the process that is in use.
Cause A user-specified process name is already in use when the monitor tries to start the
indicated process.
Effect The monitor shuts down RDF in an orderly manner.
Recovery If you can stop the process and give it another name, you can then simply restart
RDF; otherwise, you will have to alter the name of the RDF process so that the name does not
conflict with other process names.
841
Error - Unable to complete STOP UPDATE. Error error
error
is a file-system error number.
Cause The monitor was unable to send a shutdown message to an updater because of the
indicated file-system error.
Effect The monitor terminates the attempt to send STOP UPDATE messages to any other
updaters. It then sends an ABORT RDF message to all the other RDF processes and waits for
them to stop.
Recovery If any updaters have not shutdown after the monitor has sent ABORT RDF
messages, then you might have to terminate the surviving updaters manually using a TACL
STOP command.
842
Error - START prevented by RDF TAKEOVER
Cause You issued a START RDF command, but the monitor detected that RDF has already
processed a TAKEOVER command.
Effect The START RDF command fails.
Recovery The backup database is consistent and ready for use as a backup contingency
database. Perform the rest of your installation-specific operations for switching to the backup
node (for example, reroute your communications and start your applications).
If you performed the TAKEOVER operation inadvertently, you will need to issue an INITIALIZE
RDF command and resynchronize the databases.
396 Messages