| David Fishburn 2005-11-25, 11:24 am |
| Andrew wrote in news:438237fe.4747.1681692777@sybase.com
of sybase.public.sqlanywhere.mobilink:
A> We have an application using an ultralite DB on PPC 2003
A> devices. We are currently using version Mobilink version
A> 9.0.2.3131. We have a situation where the error "Error:
A> [-10035] Download failed with client error -193" appears at
A> the very end of the mobilink log and the sync fails. The
A> error seems to indicate a primary key violation. How can
A> this happen (I thought that this was taken care of as part
A> of the sync)? We do not have any unique indexes or fields
A> in the tables. How can we find out what table it is failing
A> on? We have worked on this issue and haven't gotten very
A> far. If we delete the local database and sync again,
A> everything works fine. It seems to be pretty periodic.
We have seen this in the past if you download the same PK value twice in
one synchronization.
This can happen if your download_cursor is joining to multiple tables
and you missed a join condition. So you end up downloading more data
than you intended.
In cases like this, make sure you start ML with -vcrsn -ot ml.txt and
-v+ -ot rem.txt on the remote.
Then at least you have the information to look for this.
--
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]
|