Owner manual

SDR EMS Messages
HP NonStop SQL DDL Replicator User’s Guide—545799-005
B-19
Critical Messages
Recovery. Either correct the RDF NETWORK configuration or CANCEL the SQL DDL
statement. Note that you may also configure a NETWORK inside SDR.
486
Cause. A DROP operation referenced SQL object that did not exist.
Effect. The DROP operation is ignored and SDR proceeds.
Recovery. No corrective action is needed.
487
Cause. An SDRUPDT process has abended.
Effect. The SDR monitor will restart the process. If the process continues to abend, no
DDL replication will occur.
Recovery. Contact product support.
488
Cause. An SDRUPDT process has stopped or abended, but no process-stop
message was received. This may be caused by a CPU failure.
Effect. The SDRUPDT process is restarted automatically.
Recovery. Informational message only; no corrective action is needed.
489
Cause. An SDR runtime error was detected and a transaction for a SQL DDL
statement was aborted.
Effect. The SQL DDL statement fails.
Recovery. Correct the cause of the runtime error or change the SDR configuration to
make SDR replication optional.
Target of SQL DDL operation missing
SDR updater abend
SDR updater lost
SQL DDL operation aborted