Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Ultralite synchronization error

2 posts in Ultralite Last posting was on 2011-10-12 19:47:41.0Z
Frank Daemen Posted on 2011-09-05 15:04:00.0Z
Sender: 3311.4e64dc2b.1804289383@sybase.com
From: Frank Daemen
Newsgroups: sybase.public.sqlanywhere.ultralite
Subject: Ultralite synchronization error
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4e64e4e0.34e2.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 5 Sep 2011 08:04:00 -0700
X-Trace: forums-1-dub 1315235040 10.22.241.41 (5 Sep 2011 08:04:00 -0700)
X-Original-Trace: 5 Sep 2011 08:04:00 -0700, 10.22.241.41
Lines: 24
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere.ultralite:12586
Article PK: 1048380

We have a weird problem over here.

We have an Windows Mobile 6.5 application that runs on a
ultralite db. That ultralite db synchronizes with a Mobilink
server. The consolidated db is a SQL Server db.

Version 12 is used for Ultralite and Mobilink

Now we have sometimes the problem that the sync does not
work anymore. It returns the error [10012], specifying that
the offset is not the same between the consolidated db and
the remote db. When I open up the remote db in Sybase. It
seems that the tables already in the publication I
originally created are added 3 more times and a new
publication with the same name is created containing the
same tables as in the first publication (also 4 times each
table).

The problem now is that the sync is not working anymore
because it uses both publications for doing a sync. While
one of the two has the correct offset, the other one does
not have the correct offset which result in failure of sync.

Any explanation/solution for this?


Tim McClements [Sybase] Posted on 2011-10-12 19:47:41.0Z
From: "Tim McClements [Sybase]" <mcclemenXnospam@sybase.com>
Newsgroups: sybase.public.sqlanywhere.ultralite
References: <4e64e4e0.34e2.1681692777@sybase.com>
Subject: Re: Ultralite synchronization error
Lines: 40
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4e95eedd$1@forums-1-dub>
Date: 12 Oct 2011 12:47:41 -0700
X-Trace: forums-1-dub 1318448861 10.22.241.152 (12 Oct 2011 12:47:41 -0700)
X-Original-Trace: 12 Oct 2011 12:47:41 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere.ultralite:12627
Article PK: 1048387

Hi Frank,

Can you explain what exactly you are looking at in the remote UDB regarding
the publications?

Does your application manipulate publications?

Does this problem recur consistently with a new database? Can you submit a
repro or at least the bad UDB file as a bug report?

- Tim

<Frank Daemen> wrote in message news:4e64e4e0.34e2.1681692777@sybase.com...
> We have a weird problem over here.
>
> We have an Windows Mobile 6.5 application that runs on a
> ultralite db. That ultralite db synchronizes with a Mobilink
> server. The consolidated db is a SQL Server db.
>
> Version 12 is used for Ultralite and Mobilink
>
> Now we have sometimes the problem that the sync does not
> work anymore. It returns the error [10012], specifying that
> the offset is not the same between the consolidated db and
> the remote db. When I open up the remote db in Sybase. It
> seems that the tables already in the publication I
> originally created are added 3 more times and a new
> publication with the same name is created containing the
> same tables as in the first publication (also 4 times each
> table).
>
> The problem now is that the sync is not working anymore
> because it uses both publications for doing a sync. While
> one of the two has the correct offset, the other one does
> not have the correct offset which result in failure of sync.
>
> Any explanation/solution for this?