SQL Anywhere Mobile - Protocol error Sybase 9.0.1.1751

Author

Protocol error Sybase 9.0.1.1751

tomekp

2005-11-16, 9:24 am

Hi

Question 1:

We have a problem with mobilink 9.0.1.1751. Sometimes (yes, not allways)
when user try synchronise data (aplication generated on this same sybase
UltraLite version) replication is crashed with message "Error: [-10001]
Protocol error". When user deleted databaze (remote) replication is OK. What
is wrong ? Can someone tell us ?.

Question 2: Mobilink command line:

C:\Program Files\Sybase\SQL Anywhere 9\win32\dbmlsrv9.exe

-v+ -fr -x tcpip{host=1.1.1. 1;port=2524;keep_ali
ve=1} -c
" dsn=dsn;uid=user;pwd
=pass" -o "e:\Log\CurrentLog.txt" -os 30m -zp

Sometimes in mobilink logs we have warnings like this:

W. 11/15 07:17:06. <1.4> [32]: Warning: [10017] The consolidated and remote
databases have different timestamp precisions. Consolidated database
timestamps are precise to 2 digit(s) in the fractional second while the
remote database timestamps are precise to 6 digit(s)

W. 11/15 07:17:06. <1.4> [32]: Warning: [10018] The timestamp precision
mismatch may be resolved by setting the DEFAULT_TIMESTAMP_IN
CREMENT option
on the remote database to 10000 and TRUNCATE_TIMESTAMP_V
ALUES to 'On' ---
When we do it nothik is changed

W. 11/15 07:17:06. <1.4> [32]: Warning: [10020] The timestamp precision
mismatch may affect upload conflict detection. Use the -zp option to cause
the MobiLink synchronization server to use the lowest timestamp precision
for conflict detection purposes --- this parameter is set to "on"

W. 11/15 07:17:06. <1.4> [32]: Warning: [10015] Table "table" has at least
one timestamp column. Due to a timestamp precision mismatch, uploaded
timestamps can lose precision, defeating download filtering

Did you have any suggestions ?

Regards
Tom

Reg Domaratzki $iAnywhere Solutions$

2005-11-16, 11:24 am

Answer 1 :
I've fixed a few issues dealing with protocol error in v901 since the GA
release. I'd suggest upgrade the consolidated to the latest v901 EBF and
seeing if the problem still exists in that build.

Answer 2 :
If you set the two options described in the warning to the suggested values
in your reference database (or possibly in your schema file, I'm not sure
what UL API you're using), the warnings will go away. You could also add
the -zp option to the MobiLink server start line, which is also mentioned in
the warning.

--
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 filter to "Display ALL platforms IN ALL MONTHS"

"tomekp" <tomasz. pulawski@anicasystem
.com.pl> wrote in message
news:437b40f3$1@foru
ms-2-dub...
> Hi
>
> Question 1:
>
> We have a problem with mobilink 9.0.1.1751. Sometimes (yes, not allways)
> when user try synchronise data (aplication generated on this same sybase
> UltraLite version) replication is crashed with message "Error: [-10001]
> Protocol error". When user deleted databaze (remote) replication is OK.
What
> is wrong ? Can someone tell us ?.
>
> Question 2: Mobilink command line:
>
> C:\Program Files\Sybase\SQL Anywhere 9\win32\dbmlsrv9.exe
>
> -v+ -fr -x tcpip{host=1.1.1. 1;port=2524;keep_ali
ve=1} -c
> " dsn=dsn;uid=user;pwd
=pass" -o "e:\Log\CurrentLog.txt" -os 30m -zp
>
> Sometimes in mobilink logs we have warnings like this:
>
> W. 11/15 07:17:06. <1.4> [32]: Warning: [10017] The consolidated and
remote
> databases have different timestamp precisions. Consolidated database
> timestamps are precise to 2 digit(s) in the fractional second while the
> remote database timestamps are precise to 6 digit(s)
>
> W. 11/15 07:17:06. <1.4> [32]: Warning: [10018] The timestamp precision
> mismatch may be resolved by setting the DEFAULT_TIMESTAMP_IN
CREMENT option
> on the remote database to 10000 and TRUNCATE_TIMESTAMP_V
ALUES to 'On' ---
> When we do it nothik is changed
>
> W. 11/15 07:17:06. <1.4> [32]: Warning: [10020] The timestamp precision
> mismatch may affect upload conflict detection. Use the -zp option to cause
> the MobiLink synchronization server to use the lowest timestamp precision
> for conflict detection purposes --- this parameter is set to "on"
>
> W. 11/15 07:17:06. <1.4> [32]: Warning: [10015] Table "table" has at least
> one timestamp column. Due to a timestamp precision mismatch, uploaded
> timestamps can lose precision, defeating download filtering
>
> Did you have any suggestions ?
>
> Regards
> Tom
>
>

Sponsored Links