Question Re: synchronization complete but no update take effect in Technology Q&A

synchronization complete but no update take effect

Former Member — Thu, 15 Sep 2011 04:00:13 GMT

Hello, I connect to Mobilink server using Sybase Central.

I get the following message on my side (client): ---------- Starting synchronization Connecting Upload starting Finishing upload Disconnecting Done, with errors Sync failed: Synchronization server failed to commit the upload Results of this synchronization: Failed with error: -794 Download timestamp: 2011-09-15 09:47:02.328000 Upload failed No ignored rows No part download remaining Authentication value: 0 (0x0000)

Server log file gives me this message:

[10012] The consolidated and remote databases disagree on when the last synchronization took place, the progress offsets are 11 in the consolidated database and 3 in the remote database. The remote is being asked to send a new upload that starts at the last known synchronization point I. 2011-09-15 09:44:07. <82> Progress offsets for the publications that are explicitly involved in the current synchronization I. 2011-09-15 09:44:07. <82> Subscription id 2: consolidated progress 11 and remote progress 3 I. 2011-09-15 09:44:07. <82> Progress offsets for the publications that are not explicitly involved in the current synchronization I. 2011-09-15 09:44:07. <82> Subscription id 1: consolidated progress 0 and remote progress 0 I. 2011-09-15 09:44:07. <82> Synchronization complete

I dont see any update onto my DB.

Do you have any idea on what's going on?

Thanks in advance. S

Re: synchronization complete but no update take effect

VolkerBarth — Thu, 15 Sep 2011 07:49:39 GMT

The error message tells that there's obviously a progress mismatch between your consolidated and remote databases. That means they're out of sync. This may happen when you use an older copy of the remote (e.g. a backup) to sync with the current consolidated, and the remote had successfully synced in the meantime.

(The opposite situation with a "old consolidated" can happen as well.)

That would often be a valid reason to re-build the remote. For SQL Anywhere clients, the DBMLSync -rb option may help to cure the symptom, as then the client's progress offset will be used to decide what to download. However, that may or may not lead to inconsistent data.

For Ultralite clients, the following doc part may explain more.

Re: synchronization complete but no update take effect

philippefbertrand — Thu, 15 Sep 2011 09:35:22 GMT

In situations like this, the type of remote is extremely useful. Are you using UltraLite, UltraLite J, or dbmlsync?

Is there a farm of MobiLink servers or just the one?

Re: synchronization complete but no update take effect

Former Member — Fri, 16 Sep 2011 05:58:19 GMT

thank you for this. It worked but sometimes it doesnt work as I get this result:

Sync failed: MobiLink communication error -- code: 86, parameter: 404, system code: 0 Results of this synchronization: Failed with error: -1305 Stream error code: 86 System error code: 0 Download timestamp: 2011-09-16 11:47:19.343000 Upload failed No ignored rows No part download remaining Authentication value: 0 (0x0000)

doc does not give me much info about it. Any idea on what the problem might be?

Re: synchronization complete but no update take effect

Former Member — Fri, 16 Sep 2011 06:50:23 GMT

when instead I try to sync from my client android application I get the same error

09-16 13:33:17.856: WARN/System.err(419): com.ianywhere.ultralitejni12.implementation.JniException: UltraLiteJ Error[-1305]: MobiLink communication error -- code: 57, parameter: donotshowmyparam, system code: %3

Please, what does "code: 57" mean?

Re: synchronization complete but no update take effect

VolkerBarth — Fri, 16 Sep 2011 07:52:00 GMT

MobiLink errors and warnings are documented in the docs. You may just enter the error code in the docs's "Search box".

Here is the doc for error code 57.

(Note, warnings have code > 0, errors < 0).

Besides that, I can't comment on the source of these errors. But my impression is that the new errors you have reported have a different background than the error message from your question.

Re: synchronization complete but no update take effect

philippefbertrand — Fri, 16 Sep 2011 10:04:59 GMT

When you say "connect to MobiLink using Sybase Central", how exactly did you do this? Were you using an UltraLite tool?

Re: synchronization complete but no update take effect

Former Member — Fri, 16 Sep 2011 10:23:04 GMT

the remote is Mobilink12. as client we use ultralite12 and an android application.

Re: synchronization complete but no update take effect

philippefbertrand — Fri, 16 Sep 2011 10:51:47 GMT

MobiLink is not a remote - it is the technology that synchronizes the remotes with a consolidated. Remote and client mean the same thing.

But you said in your original question that you used Sybase Central. I'm assuming you use the ul sync tool. Where did you get the client database from? Did you copy it from a device?

Is there just one MobiLink server or a farm?

Re: synchronization complete but no update take effect

philippefbertrand — Fri, 16 Sep 2011 11:06:41 GMT

In addition to Caution that @Volker provided a link to (copied below), I would add the following:

You must not copy an UltraLite database that has been synchronized from on client to another, or share ML remote ids. If you wish to copy a database, you must reset the ML remote id. Each client must have a unique ML remote id to maintain independent state.

Caution

Because UltraLite increments the progress counter each time a synchronization occurs, you cannot synchronize an UltraLite database to different consolidated databases. If the progress counter value is not zero and does not match that sequence number stored in the consolidated database, MobiLink synchronization reports an offset mismatch and synchronization fails. You cannot replace an UltraLite database with a backup copy if the progress counter is older than the current value.

Re: synchronization complete but no update take effect

Former Member — Fri, 16 Sep 2011 11:51:26 GMT

sorry I was wrong in calling Mobilink as remote. I use SybaseCentral 6.1.0.6420 and I downloaded it from internet. Is not a farm but just one server.

Re: synchronization complete but no update take effect

VolkerBarth — Fri, 16 Sep 2011 13:11:12 GMT

I'm quite sure Philippe would like to know where you get the remote database from (i.e. whether you copied that from a device which might have already synced), not the SQL Anywhere software...

Re: synchronization complete but no update take effect

Former Member — Mon, 19 Sep 2011 08:54:35 GMT

Hello, it was not me in doing that but in order to generate remote database has been followed those steps: - through Sybase Central, Click on: Mobilink 12 > ServerName > Synchronization models - right key on db - click on "Deploy..." - choose "Deploy immediately using last deployment settings" - Finish.

Thank you in advance, S

Re: synchronization complete but no update take effect

philippefbertrand — Mon, 19 Sep 2011 11:06:41 GMT

That helps...I asked our MobiLink plugin for SYbase Central person to look at your question.

Re: synchronization complete but no update take effect

Former Member — Mon, 19 Sep 2011 11:25:20 GMT

That doesn't tell us whether you are creating a new remote database when deploying your synchronization model, or deploying to an existing remote database. To see what the "last deployment settings" are, choose the "Run this wizard initialized with last deployment settings" and note whether you deploying to a new remote database or an existing remote database.

Re: synchronization complete but no update take effect

Former Member — Mon, 19 Sep 2011 11:42:43 GMT

Here's what I think led to your original problem.

You used a synchronization model to deploy to an UltraLite remote database (UDB file) on your PC, and synchronized that at least once from the PC.
-> That changes the UDB file to have a remote ID and a non-zero progress offset.
You then copied that UDB file to your Android device and synchronized several times.
-> Each sync bumps up the progress offset in the Android copy of the UDB file, but not in the PC copy.
You then redeployed to the PC copy of the UDB file.
-> The PC copy will then have the same remote ID, but a much earlier progress offset, causing the error whether you sync it from the PC or copy it to the Android device and sync it.

You either needed to copy the UDB back from the Android device before redeploying to it, or not copy a synchronized UDB file to your Android device.

Re: synchronization complete but no update take effect

Former Member — Mon, 19 Sep 2011 12:09:09 GMT

deploying is to a new remote database. Thanks, S

Re: synchronization complete but no update take effect

Former Member — Mon, 19 Sep 2011 12:55:05 GMT

A new remote database won't have a remote ID and (for UltraLite remotes) the progress offset will be zero. So if you are deploying to a new UltraLite remote, it should create a new UDB file that is "clean" for copying to different remotes.

Did you synchronize the new UDB file on the PC before copying to the Android device?
Is your application explicitly setting the remote ID?

Re: synchronization complete but no update take effect

Former Member — Mon, 19 Sep 2011 15:49:02 GMT

yes, I did. That's because I try first if synchronization works with SybaseCentral and then with my application. I do not set any remote ID, I just set the following params: httpParms.setHost("xxx"); httpParms.setPort(xxx); syncParms.setUserName("xxx"); syncParms.setPassword("xxx"); syncParms.setPublications("xxx");

Re: synchronization complete but no update take effect

VolkerBarth — Mon, 19 Sep 2011 15:59:01 GMT

As Graham has stated, once you do sync, you will automatically set a remote ID. See his answer below to understand the effect and cause...