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

731
RDF monitor started
Cause The operator issued a START RDF command.
Effect The RDF monitor process is running and starting up the other RDF processes.
Recovery This is an informational message; no recovery is required.
732
Unable to create exception file filename, error error
filename
is the name of the exception file that the updater was trying to create.
error
is the file-system error number that identifies the specific error.
Cause An updater process encountered an error while attempting to create an exception
file. The message includes the file-system error number and the name of the exception file that
the updater was trying to create.
Effect This is a catastrophic error; the updater abends, and RDF stops.
Recovery Determine the cause of the error, correct the condition, and then restart RDF.
733
Stopping update for SQL DDL operation on [ANSI-object-type ANSI-name,
Partition partition-id,] file filename
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 is affected by the DDL operation.
partition-id
is the partition ID of the SQL/MX object that is affected by the DDL operation.
filename
is the Guardian file name of the file that is affected by the DDL operation.
Cause The updater has found a Stop-RDF-Updater record in the image trail. This special
record is generated in the TMF audit trail on the primary system when an SQL DDL operation
WITH SHARED ACCESS involving the specified file has completed. Each updater will stop
when it reaches this record in the image trail.
Effect The updaters stop.
Recovery When all updaters have stopped, you must perform the same SQL DDL operation
on the RDF backup system that was originally performed on the primary system. When this
operation has been completed, start the updaters again with the START UPDATE command.
NOTE: You must not start the updaters until you have performed the DDL operation.
Otherwise, you will corrupt your database on the RDF backup system.
734
Inappropriate message type type received {from process-id cpu,pin |
from process processname} [, program file programfile]
type
is the message number in the received message, which was not one of the codes recognized
by the RDF process.
cpu,pin
is the cpu,pin number of the process that sent the message.
350 Messages