| Greg Fenton 2005-05-01, 8:27 pm |
| MJN wrote:
>
> Firstly to control the size of the transaction log u must use the -x option
> in conjunction with setting delete_old_logs to ON and lastly setting the
> directory of the old logs in the subscription extended options?
>
Basically, you set DELETE_OLD_LOGS to ON and you run dbmlsync with the
"-x" parameter (no need to specify a size with it...I typically don't).
If all of the changes in the transaction log are synchronized, then
the transaction log will be deleted at the end of the synchronization.
However, realize that if you have multiple publications that you need to
have fully synchronized *all* of the publications for the deletion to
take place.
> Secondly if delete_old_logs is applied to all remotes and the consolidated.
> I noticed during the last sync where only remote1 had tables updated. After
> all the remotes synced with the consolidated one remote (remote4) did not
> receive the updated rows that were inserted into remote1.
The deletion of the transaction log of the consolidated has *no* effect
on synchronization. The transaction log is only scanned by the ML
*client* (dbmlsync) to determine the data needs to be uploaded. The
MobiLink server uses only the synchronization scripts to determine the
data that is to be downloaded (using the download_cursor and
download_delete_curs
or).
If data is not being sent to remote4, it is because the result set of
the download_cursor (that runs against the consolidated) did not include
those rows, or because for some reason those rows were rejected on the
remote (e.g. child rows in a FK relationship where the parent row does
not exist on the remote).
> Lastly all remotes reported that the sync was successful but unfortunately I
> don't have the log of remote4 any longer due to restarting mlsync and thus
> being over written.
>
Again, the log file of remote4 should only be deleted in the event of a
successful synchronization. Restarting dbmlsync should not affect this
behaviour.
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|