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

Effect The updaters are stopped, but the backup database is not in a consistent state
corresponding to the stop update timestamp.
Recovery Restart the updaters. If you still need to bring the backup database to a consistent
state, do the following. Wait for the updaters to catch up and then issue a new stop update to
time command, specifying a new timestamp.
705
File Open Error error on [ANSI-object-typeANSI-name, Partition
partition-id,] file filename
error
is the file-system error number that identifies the specific error.
ANSI-object-type
is the ANSI object type (for example, table, index, and so on). See Table 16-1 (page 295) for
a list of possible ANSI object types.
ANSI-name
is the ANSI name of the SQL/MX object that encountered the error.
partition-id
is the partition ID of the SQL/MX object that encountered the error.
filename
is the Guardian file name of the file that encountered the error.
sno
is the sequence number of the file that encountered the error.
rba
is the relative byte address within the file where the error occurred.
Cause A file-system error occurred while RDF was attempting to open a file, table, or process.
The message includes both the file-system error number and the name of the file, table, or
process that was to be opened.
Effect If this message is issued by an updater process, see Table 5-2 in the RDF manual to
determine the appropriate recovery actions.
The extractor retries OPEN calls for the audit-trail files if the error is 11 (file missing), 12 (file
in use), or 59 (file is bad). Those errors might occur while the audit-trail file is being restored
to disk.
The receiver retries OPEN calls for the image files if the error is 11 (file missing), 12 (file in
use), or 59 (file is bad). Those errors might occur while the image file is being restored to disk.
Recovery If this message is issued by an updater process, see Table 5-2 (page 123) to determine
the appropriate recovery actions.
706
RDF monitor shutdown complete
Cause The monitor process has stopped itself and all RDF processing as the result of an
operator-initiated stop or a catastrophic failure.
Effect The monitor sends a stop message to all RDF processes, and they all successfully shut
down.
Recovery If the operator issued a STOP TMF or STOP RDF command, this message is merely
informational and no recovery is required.
If this message is unexpected, check the RDF log to determine the cause of the failure.
You can attempt to correct the underlying problem, and then restart RDF. If you do that,
however, you should select a convenient time to stop TMF and verify that the primary and
backup databases are synchronized.
You should also check the event log to determine whether the shutdown and startup proceeded
without error. If that is not the case, no recovery is possible.
344 Messages