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

915
Drain operation complete but a primary volume is down
Cause
A STOP RDF, DRAIN or STOP RDF, REVERSE command has completed but RDF has detected
that a volume on the primary node is down.
Effect
Any transactions that touched the affected volume that were active when the volume went down
are unresolved (on both the primary and backup systems). If this event is the result of a STOP
RDF, REVERSE, the REVERSE trigger is not executed.
Recovery
Repair and bring up the affected volume, restart RDF and repeat the operation.
916
File create error err on filename
err
is a Guardian error number.
filename
is the name of the file that could not be created.
Cause
The process that reported this event could not create the specified file. The attempt to create the
file returned the specified Guardian error.
Effect
The file is not created and the effect on RDF depends on which process reported the error and
on what it was attempting to do at the time.
Recovery
If possible, the user should attempt to correct the underlying problem or seek assistance from
their service provider.
917
Shared access DDL operation encountered while DRAIN or REVERSE is pending
Cause
A STOP RDF, DRAIN (or REVERSE) operation is being processed and the RDF extractor
encountered a shared access DDL operation in the TMF audit trail.
Effect
These two operations cannot be processed concurrently, which causes RDF to abort.
Recovery
Restart RDF and the shared access DDL operation will be processed as normal. Having completed
the shared access DDL operation, a new STOP RDF, DRAIN (or REVERSE) command can be
issued.
918
STOP TMF record encountered while DRAIN or REVERSE is pending
Cause
A STOP RDF, DRAIN (or REVERSE) operation is being processed and the RDF extractor
encountered a STOP TMF record in the TMF audit trail.
Effect
These two operations cannot be processed concurrently, which causes RDF to abort.
404 Messages