SQL Anywhere Mobile

Author

Urgent...

Sanjay

2005-06-27, 11:24 am

ASA 9.0.1 (1922)

One of my client is getting this error.

W. 06/27 12:02:30. <1.5> [01;tech=218]: 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. 06/27 12:02:30. <1.5> [01;tech=218]: Progress offsets for the
publications that are explicitly involved in the current synchronization
I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 4: consolidated
progress 1211952 and remote progress 1211952
I. 06/27 12:02:30. <1.5> [01;tech=218]: Progress offsets for the
publications that are not explicitly involved in the current synchronization
I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 5: consolidated
progress 1040110 and remote progress 930992
I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 6: consolidated
progress 1615802 and remote progress 930895
I. 06/27 12:02:30. <1.5> [01;tech=218]: Synchronization failed

I can see that Subscription id 5 & 6 progress does not match.
Do i have to reset his db on handheld inorder to fix it or can i do it from
consolidate db?
Also how can i prevent this from occurring in future?

TIA

Sanjay

Sanjay

2005-06-28, 9:24 am

Solved it by -rb option.
But still doesn't know how it happenned.

"Sanjay" <sas@sasintl.com> wrote in message news:42c025cd$1@foru
ms-1-dub...
> ASA 9.0.1 (1922)
>
> One of my client is getting this error.
>
> W. 06/27 12:02:30. <1.5> [01;tech=218]: 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. 06/27 12:02:30. <1.5> [01;tech=218]: Progress offsets for the
> publications that are explicitly involved in the current synchronization
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 4: consolidated
> progress 1211952 and remote progress 1211952
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Progress offsets for the
> publications that are not explicitly involved in the current
synchronization[colo
r=darkred]
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 5: consolidated
> progress 1040110 and remote progress 930992
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 6: consolidated
> progress 1615802 and remote progress 930895
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Synchronization failed
>
> I can see that Subscription id 5 & 6 progress does not match.
> Do i have to reset his db on handheld inorder to fix it or can i do it[/color]
from
> consolidate db?
> Also how can i prevent this from occurring in future?
>
> TIA
>
> Sanjay
>
>

Reg Domaratzki $iAnywhere Solutions$

2005-06-28, 11:24 am

This should have been followed in the MobiLink log with another
synchronization from "01;tech=218" after the "remote was asked to send a new
upload that starts at the last known synchronization point". Does the
MobiLink log show a successful synch from "01;tech=218" after this WARNING
appears?

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"Sanjay" <sas@sasintl.com> wrote in message news:42c025cd$1@foru
ms-1-dub...
> ASA 9.0.1 (1922)
>
> One of my client is getting this error.
>
> W. 06/27 12:02:30. <1.5> [01;tech=218]: 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. 06/27 12:02:30. <1.5> [01;tech=218]: Progress offsets for the
> publications that are explicitly involved in the current synchronization
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 4: consolidated
> progress 1211952 and remote progress 1211952
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Progress offsets for the
> publications that are not explicitly involved in the current
synchronization[colo
r=darkred]
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 5: consolidated
> progress 1040110 and remote progress 930992
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Subscription id 6: consolidated
> progress 1615802 and remote progress 930895
> I. 06/27 12:02:30. <1.5> [01;tech=218]: Synchronization failed
>
> I can see that Subscription id 5 & 6 progress does not match.
> Do i have to reset his db on handheld inorder to fix it or can i do it[/color]
from
> consolidate db?
> Also how can i prevent this from occurring in future?
>
> TIA
>
> Sanjay
>
>

Sanjay

2005-06-28, 11:24 am

This should have been followed in the MobiLink log with another
synchronization from "01;tech=218" after the "remote was asked to send a
new
upload that starts at the last known synchronization point". Does the
MobiLink log show a successful synch from "01;tech=218" after this WARNING
appears?

S>>Yes it does...
since i have 3 publications, i had to sync. explicitly with all of them (
which i think made progress
in ml_subscription equal to remote progress) before i can switch back to
regular parameters.

Again how did this happenned? He was having problem synchronizing because ml
was trying to insert
a row(insteading of updating), which already exists in middleware database.
He did not deleted the row and added again after successfull sync. from
remote, I am sure because there is no provision in the
program to do that.
After i delete that row from middleware db, this started to happen.
I have done this in the past without any problem..not this time thou

- Sanjay

"Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
wrote in message news:42c16a0b$1@foru
ms-1-dub...
> This should have been followed in the MobiLink log with another
> synchronization from "01;tech=218" after the "remote was asked to send a
new
> upload that starts at the last known synchronization point". Does the
> MobiLink log show a successful synch from "01;tech=218" after this WARNING
> appears?
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL
>
> "Sanjay" <sas@sasintl.com> wrote in message
news:42c025cd$1@foru
ms-1-dub...
consolidated[color=d
arkred]
place.[color=darkred]
> known
> synchronization
> from
>
>

Reg Domaratzki $iAnywhere Solutions$

2005-06-28, 1:24 pm

The most common cause of this problem is that the remote was recovered from
a backup, and the transaction logs to get the database back to the point of
failure were not applied. Therefore, the recovered remote does not believe
that it has sent anything greater than offset 930992 to the consolidated,
but the consolidated received this upload from the remote database that was
not properly recovered.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"Sanjay" <sas@sasintl.com> wrote in message news:42c16f58@forums
-1-dub...
> This should have been followed in the MobiLink log with another
> synchronization from "01;tech=218" after the "remote was asked to send a
> new
> upload that starts at the last known synchronization point". Does the
> MobiLink log show a successful synch from "01;tech=218" after this
WARNING
> appears?
>
> S>>Yes it does...
> since i have 3 publications, i had to sync. explicitly with all of them (
> which i think made progress
> in ml_subscription equal to remote progress) before i can switch back to
> regular parameters.
>
> Again how did this happenned? He was having problem synchronizing because
ml
> was trying to insert
> a row(insteading of updating), which already exists in middleware
database.
> He did not deleted the row and added again after successfull sync. from
> remote, I am sure because there is no provision in the
> program to do that.
> After i delete that row from middleware db, this started to happen.
> I have done this in the past without any problem..not this time thou
>
> - Sanjay
>
>
> "Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
> wrote in message news:42c16a0b$1@foru
ms-1-dub...
> new
WARNING[color=darkre
d]
> http://www.ianywhere.com/developer/product_manuals
> news:42c025cd$1@foru
ms-1-dub...
> consolidated
> place.
synchronization[colo
r=darkred]
consolidated[color=d
arkred]
consolidated[color=d
arkred]
consolidated[color=d
arkred]
>
>

Sponsored Links