SQL Anywhere Mobile - synchronization failed on ipaq

Author

synchronization failed on ipaq

wayne

2005-10-27, 8:20 am

after i test my pocketbuilder application on the desktop, synchronization my
remote db to oracle sucessfully, i deploy the application to my ipaq, copy
the remote db to ipaq, and synchronization failed. the mlserver log is

W. 10/08 14:42:16. <1.5> [z331]: Warning: [10012] The consolidated and
remote databases disagree on when the last synchronization took place. The
remote is being asked to send a new upload that starts at the last known
synchronization point
I. 10/08 14:42:16. <1.5> [z331]: Progress offsets for the publications that
are explicitly involved in the current synchronization
I. 10/08 14:42:16. <1.5> [z331]: Subscription id 20: consolidated progress
663387 and remote progress 348022
I. 10/08 14:42:16. <1.5> [z331]: Synchronization failed

i changed a mluser,synchronizati
on remains failed.the mlserver log is

W. 10/08 15:03:59. <1.5> [z340]: Warning: [10012] The consolidated and
remote databases disagree on when the last synchronization took place. The
remote is being asked to send a new upload that starts at the last known
synchronization point
I. 10/08 15:03:59. <1.5> [z340]: Progress offsets for the publications that
are explicitly involved in the current synchronization
I. 10/08 15:03:59. <1.5> [z340]: Subscription id 26: consolidated progress
351458 and remote progress 348580
I. 10/08 15:03:59. <1.5> [z340]: Synchronization failed

anybody can help me?

Greg Fenton

2005-10-27, 8:20 am

wayne wrote:
> I. 10/08 14:42:16. <1.5> [z331]: Subscription id 20: consolidated progress
> 663387 and remote progress 348022

This indicates that you have already synchronized a database with ML
user (or synchronization user) "20", whose last offset was 663387. Now
you are attempting to synch another database whose last synch'ed log
offset is 348022, using the same "20" ML username.

You should not be using the same ML username on different remote
databases. If you want to re-use an ML username on a new remote
database, you need to first drop the user from the consolidated using a
tool such as the "dbmluser" command line or Sybase Central.

Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

David Fishburn

2005-10-27, 8:20 am

Greg Fenton <greg. fenton_NOSPAM_@ianyw
here.com> wrote in
news:43486d36$1@foru
ms-1-dub of sybase.public.sqlanywhere.mobilink:

GF> wayne wrote:
GF>> I. 10/08 14:42:16. <1.5> [z331]: Subscription id 20: consolidated
GF>> progress 663387 and remote progress 348022
GF>
GF> You should not be using the same ML username on different remote
GF> databases. If you want to re-use an ML username on a new remote
GF> database, you need to first drop the user from the consolidated using
GF> a tool such as the "dbmluser" command line or Sybase Central.

Or, if in fact you are using the same machine, but simply rebuilt the
remote database (like you would in development mode over and over
again), then simply moving to 902 will address this.

Please ALWAYS include version and MORE importantly BUILD number
with EACH post (dbeng9 -v).

--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng9 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm

Developer Community / Whitepapers
http://www.ianywhere.com/developer

CaseXpress - to report bugs
http://casexpress.sybase.com

CodeXchange - Free samples
[url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]

Sponsored Links