HP NonStop RDF J-series RVUs Management Manual page 459

error#
is the file-system error number that identifies the specific error.
filename
is the name of the image trail file associated with the error.
Cause The COPYAUDIT command encountered the specified error while attempting to
write data into the specified image file on the local image trail volume.
Effect
The COPYAUDIT command aborts.
Recovery
See the Operator Messages Manual for a description of the error code. For additional
details about understanding and correcting file-system errors, see the Guardian Procedure Errors
and Messages Manual. If possible, correct the error and reenter the COPYAUDIT command.
Otherwise, see your system manager.
You are about to copy audit records from remote-system to local-system
Are you sure you want to proceed [Y/N] ?
remote-system
is the name of the RDF backup system that received the most audit.
local-system
is the name of the local RDF system that received the least audit.
Cause
You entered a COPYAUDIT command and receive this message as a prompt for
confirmation that you want to proceed with the command's execution.
Effect If you respond YES or Y, RDF executes the command. If you respond NO or N, the
command terminates.
Recovery This is an informational message; no recovery is required.
You are about to unpin a file that the extractor needs. Are you sure
you want to proceed?
Cause
You have asked RDFCOM to unpin a file that is currently needed by the extractor. If
you respond "yes," the file is unpinned and TMF can rename it. If the file is renamed, RDF
cannot be restarted until you restore the file.
Effect
RDFCOM suspends until you respond to the prompt.
Recovery
Respond "yes" or "no" to the prompt.
You are attempting a TAKEOVER operation immediately after the receiver
has crashed. Please contact your HP analyst before proceeding with the
TAKEOVER operation.
Cause RDFCOM has detected that the receiver stopped prematurely the last time it was
running. Because you are attempting the takeover operation before RDF has been allowed to
restart, the probability is high that your database is already inconsistent with respect to
transaction boundaries. That is, for some transactions, all audit data might not have been
applied to database.
Effect The database might be inconsistent.
Recovery Performing the takeover might still leave the database inconsistent. If you
nevertheless choose to perform the takeover operation, you must first manually repair the last
image file on disk. Before proceeding, contact the Global Mission Critical Solution Center
(GMCSC) or your service provider.
You are logged on as user-id. To issue this command you must be super-id.
Cause
You tried to issue a critical RDFCOM command, but you are not the super-user who
initialized the RDF configuration.
Effect The command fails.
Recovery Log on as the super-user who initialized your RDF configuration.
RDFCOM Messages 459