The following errors can occur on a SQL Remote system:
Row not found errors See Row not found errors.
Referential integrity errors See Referential integrity errors.
Duplicate primary key errors See Duplicate primary key errors.
By default, when an error occurs, the Message Agent (dbremote) prints the error in its log output window. The Message Agent (dbremote) can print more information in the output messages file than in the messages window.
The Message Agent (dbremote) messages log file includes the following information:
To print an error to the output log file, run the Message Agent (dbremote) with the -o option. See Message Agent (dbremote).
When an error occurs, you can configure SQL Remote to:
Run an error-handling procedure By default, no procedure is called. However, you can use the replication_error database option to specify a stored procedure to be called by the Message Agent (dbremote) when an error occurs. See Run an error-handling procedure.
For example, you can configure SQL Remote to:
Send portions of a remote database's output log to the consolidated database and written to a file. See Collect errors from the remote database.
Send an email notification when an error occurs at a remote database. See Receive email notification about remote database errors.
Ignore the error There might be instances when you do not want to the Message Agent (dbremote) to report an error. For example, you can choose to ignore an error when you know the conditions under which the error occurs and you are sure that the error does not produce inconsistent data. See Ignoring replication errors.
Run an error-handling procedure
Ignoring replication errors
| Discuss this page in DocCommentXchange. Send feedback about this page using email. |
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1 |