Why remote DB with mobilink sync get corrupted during connection issue back to console?

[Former Member]

HI, we have observed that most of the time the remote DB get corrupted if there is a connection failure ( line down ) back to console server. is there any way to prevent this ? we have set the sync interval from every 2 min to 10 min depends on the publication respectively. the corruption happening in all the version of Sql anywhere ( ver 10,11 and 12).

TIA vhm

[Breck_Carter]

What is the exact symptom (messages, etc) for the "corrupted" condition?

[Former Member]

Exact client software type (UL, SA or ULJ) and versions and build numbers will also be required.

[Former Member]

Client software type is SA and version 10,11 and 12 and the message displayed is "missing Log files" .

[VolkerBarth]

Which build numbers are you using?

[Former Member]

version 10.0.1 build 3415 version 11.0.1 build 2044

[regdomaratzki]

If the error is "missing log files", we'll need to know some more information :

1)Where are you storing the database file and active transaction log?

2) What is the start line for the dbeng12/dbsrv12 process that starts the database engine at the remote site?

3) What is the start line for the dbmlsync process at the remote site?

4) Do you perform any backups that rename,restart or delete the active transaction log?

Thanks, Reg

[Former Member]

Without knowing exactly what you mean by "corruption" I can only guess that you might be doing implicit or explicit COMMITs in your synchronization scripts, which breaks MobiLink's built-in recovery from dropped connections. As stated in the Mobilink documentation:

There should be no implicit or explicit commit or rollback in your SQL synchronization scripts or the procedures or triggers that are called from your SQL synchronization scripts. COMMIT or ROLLBACK statements within SQL scripts alter the transactional nature of the synchronization steps. If you use them, MobiLink cannot guarantee the integrity of your data in the event of a failure.