Handling errors and warnings in event hook procedures

Referential integrity violations occur when rows in the download violate foreign key relationships on the remote database. Use the following event hooks to log and handle referential integrity violations:

The sp_hook_dbmlsync_ml_connect_failed event hook allows you to retry failed attempts to connect to the MobiLink server using a different communication type or address. If connection ultimately fails, dbmlsync calls the sp_hook_dbmlsync_communication_error and sp_hook_dbmlsync_all_error hooks.

See sp_hook_dbmlsync_ml_connect_failed.

Each time a dbmlsync error message is generated, the following hooks are called:

First, depending on the type of error, one of the following hooks is called: sp_hook_dbmlsync_communication_error, sp_hook_dbmlsync_misc_error, or sp_hook_dbmlsync_sql_error. These hooks contain information specific to the type of error; for example, sqlcode and sqlstate are provided for SQL errors.
Next, sp_hook_dbmlsync_all_error is called. This hook is useful for logging all errors that occur.

See:

If you want to restart a synchronization in response to an error, you can use the user state parameter in sp_hook_dbmlsync_end.

See sp_hook_dbmlsync_end.

By default, synchronization stops when an unhandled error is encountered in an event hook procedure. You can instruct the dbmlsync utility to ignore these errors by supplying the -eh option.

See IgnoreHookErrors (eh) extended option.

Handling errors and warnings in event hook procedures

Handling RI violations

Handling MobiLink connection failures

Handling dbmlsync errors

Ignoring errors