SQL Anywhere Mobile - Problems with memory the pocket

Author

Problems with memory the pocket

OMTECH

2005-07-15, 8:25 pm

1) in my pocket I have Sybase 9.0.2. and my problem is that
in each synchronization I have left less space in the
memory. I assume that it is by the log, I am using in the
remote base the option Delete_old_logs = ON, and in the
dbmlsync use the command lines - x 3M, this makes that the
file log is divided in several with the format YYMMDDXX, but
never it delete some of the logs.

What more I can use to save space in the memory? or I am
using the incorrect options....

2) also before synchronizing I have that manually to adjust
the memory, and to assign more to the storage part... if I
don't make this I have problems in the synchronization. How
can I solve this?

3) In my remote base it removes him some tables and then
unload in a new base, but when I use this new base in the
pocket to the moment to synchronize me it goes out error
with the log and I cannot synchronize... Therefore I have to
continue using the previous base (that you bigger).

My objective with all this is to save I space by heart.

THANK YOU

David Fishburn

2005-07-22, 9:26 am

OMTECH wrote in news:42d828bd.7838.1681692777@sybase.com
of sybase.public.sqlanywhere.mobilink:

O> 1) in my pocket I have Sybase 9.0.2. and my problem is that
O> in each synchronization I have left less space in the
O> memory. I assume that it is by the log, I am using in the
O> remote base the option Delete_old_logs = ON, and in the
O> dbmlsync use the command lines - x 3M, this makes that the
O> file log is divided in several with the format YYMMDDXX, but
O> never it delete some of the logs.

Based on your previous posts, this is most likely due to you having:
1. Multiple synchronization users
OR
2. Multiple publications
OR
3. A combination of the above.

The logs can ONLY be deleted after ALL synchronization users and
publication combinations have successfully synchronized.

This is the reason I went in great length to post how you can accomplish
this by changing your synchronization scripts and adding 1 additional
table.

O> What more I can use to save space in the memory? or I am
O> using the incorrect options....

If you have done the above then you are few choices. Limit the amount
of data you download or get a larger memory card.

O> 2) also before synchronizing I have that manually to adjust
O> the memory, and to assign more to the storage part... if I
O> don't make this I have problems in the synchronization. How
O> can I solve this?

All related to the above.

O> 3) In my remote base it removes him some tables and then
O> unload in a new base, but when I use this new base in the
O> pocket to the moment to synchronize me it goes out error
O> with the log and I cannot synchronize... Therefore I have to
O> continue using the previous base (that you bigger).
O>
O> My objective with all this is to save I space by heart.

If you follow the instructions from 1), or more importantly the details
instructions I gave in previous posts so you ONLY have 1 synchronization
user on the client, I suspect these problems will go away.

--
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