MobiLink Synchronization Reference
Stored Procedures
Client event-hook procedures
Use this stored procedure to add custom actions immediately before synchronization is complete.
| Name | Values | Description |
|---|---|---|
| restart (in|out) | True|False | If set to true then, instead of shutting down, dbmlsync begins a new synchronization subject to the same scheduling parameters that applied to the synchronization it just completed. If the field is false (the default) then dbmlsync shuts down or restarts according to its command line arguments. |
| exit code (in) | number | If set to anything other than zero (the default), this represents a synchronization error. |
| publication_n (in) | publication name | The publications being synchronized, where n is an integer. There is one publication_n entry for each publication being uploaded. |
| MobiLink user (in) | MobiLink user name | The MobiLink user for which you are synchronizing. |
| upload status (in) | retry | committed | failed |
Specifies the status returned by the MobiLink synchronization server when dbmlsync attempted to verify receipt of the upload stream.
retry The MobiLink synchronization server and dbmlsync had different values for the log offset from which the upload stream should start. The upload stream was not committed by the MobiLink synchronization server. The dbmlsync utility will attempt to send another upload stream starting from a new log offset. committed The upload stream was received by the MobiLink synchronization server, and committed. failed The MobiLink synchronization server did not commit the upload stream. |
| script version (in) | script version name | The MobiLink script version to be used for the synchronization. |
If a procedure of this name exists, it is called as the last event during synchronization.
Actions of this procedure are committed immediately after execution.
There are cases where dbmlsync never terminates after synchronizing the first publication, so the second will never be synchronized:
If an sp_hook_dbmlsync_end hook is defined so that the hook always sets the restart parameter to true, and you specify multiple publications on the dbmlsync command line in the form -n pub1, -n pub2, etc., then dbmlsync repeatedly synchronizes the first publication and never synchronizes the second.
Customizing the client synchronization process
Synchronization event hook sequence