RDF System Management Manual for J-series and H-series RVUs (RDF Update 13)

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 ID who initialized the
RDF configuration.
Effect
The command fails.
Recovery
Log on as the super ID who initialized your RDF configuration.
You cannot add more than 48 network records
Cause
The current limit for the number of RDF subsystems in your RDF network is 48 and you have
attempted to add 49.
Effect
The configuration command fails.
Recovery
Do not add any more network records.
You cannot alter MAPFILE on the backup system if the primary system is
available
Cause
During execution of an ALTER VOLUME command on the backup system, RDFCOM determined
that the primary system is accessible.
Effect
The command fails.
Recovery
Reenter the command on the primary system.
You cannot alter MAPLOG on the backup system if the primary system is
available
RDFCOM Messages 487