SQL Anywhere Mobile - synchronization error for volume of information

Author

synchronization error for volume of information

Luis Ponce Ibarra - Hotmail

2005-08-02, 11:25 am

we are synchronizing using as consolidated database oracle 9i and like
remote database sybase 9.0.2 in mobile pocket 2002 y mobile2003. To
synchronize we use pocketbuilder 1.5.
In the remote database we use a single publication we have the option
Delete_old_logs = ON also uses for the synchronization the parameter - x 3M
and that helps us to that go fading the log.
But we have a problem it data it we synchronize to the mobile it is enough
we have around 40.000 and another information that it causes that to the
moment to synchronize we have to be moving the memory of the pocket so that
the synchronization doesn't fall in the pocket the message that normalemnte
comes out it is the following one:

/ * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * /
Running on Windows CE 3.0 Build 11171
2044K of memory used for caching
Using to maximum page size of 2048 bytes
Database server started at Fri Jul 29 2005 11:15
Trying to start SharedMemory link...

SharedMemory link started successfully

Now accepting requests
Starting database "salestrack" (\ Program Files\Sybase\ASA9\sa
lestrack.db)
at Fri Jul 29 2005 11:15
Transaction log: SalesTrack.log
Starting checkpoint of "salestrack" (salestrack.db) at Fri Jul 29 2005 11:15
Finished checkpoint of "salestrack" (salestrack.db) at Fri Jul 29 2005 11:15
Database "salestrack" (salestrack.db) started at Fri Jul 29 2005 11:15
Starting checkpoint of "salestrack" (salestrack.db) at Fri Jul 29 2005 11:30
Finished checkpoint of "salestrack" (salestrack.db) at Fri Jul 29 2005 11:30
* * * ERROR * * * Assertion failed: 201848 (9.0.2.3044)
Checkpoint log: write to \ Program Files\Sybase\ASA9\sa
lestrack.db failed
with status 2: filesystem may be full

Connection terminated abnormally

Disconnected SharedMemory client's AppInfo: HOST=Pocket_PC;OS=Wi
ndows CE 3.0
Build 11171; PID=0x93c94eba;THREA
D=0x92630b86;EXE=\Pr
ogram
Files\Sybase\ASA9\db
mlsync.exe;VERSION=9.0.2. 3044;API=DBLIB;TIMEZ
ONEADJUSTME
NT=-300

/ * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * /

If during the synchronization process especially of the internal process
that executes the pocket to ascend the it dates of the events donwload, we
move the memory it works but that generates us complications that it should
always be been pending of the memory and if we neglect ourselves falls.
In the pocket the error that usually comes out is the -301 that it means
"Internal database error %1--transaction rolled back"
Some way exists of overcoming this problem without necessity of being moving
the memory or that they recommend me

Reg Domaratzki $iAnywhere Solutions$

2005-08-03, 11:24 am

The log file and database file will need to grow while the download stream
is being applied. If the device doesn't have enough memory to hold all the
information you want to send down, your either going to have to reduce the
size of your downloads or increase the amount of space on the device.

Exactly how large does the log file become when you download 40,000 records?

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

"Luis Ponce Ibarra - Hotmail" < luisponceibarra@hotm
ail.com> wrote in message
news:42ef9fac@forums
-1-dub...
> we are synchronizing using as consolidated database oracle 9i and like
> remote database sybase 9.0.2 in mobile pocket 2002 y mobile2003. To
> synchronize we use pocketbuilder 1.5.
> In the remote database we use a single publication we have the option
> Delete_old_logs = ON also uses for the synchronization the parameter - x
3M
> and that helps us to that go fading the log.
> But we have a problem it data it we synchronize to the mobile it is enough
> we have around 40.000 and another information that it causes that to the
> moment to synchronize we have to be moving the memory of the pocket so
that
> the synchronization doesn't fall in the pocket the message that
normalemnte
> comes out it is the following one:
>
> / * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
> * * * * * * /
> Running on Windows CE 3.0 Build 11171
> 2044K of memory used for caching
> Using to maximum page size of 2048 bytes
> Database server started at Fri Jul 29 2005 11:15
> Trying to start SharedMemory link...
>
> SharedMemory link started successfully
>
> Now accepting requests
> Starting database "salestrack" (\ Program Files\Sybase\ASA9\sa
lestrack.db)
> at Fri Jul 29 2005 11:15
> Transaction log: SalesTrack.log
> Starting checkpoint of "salestrack" (salestrack.db) at Fri Jul 29 2005
11:15

> Finished checkpoint of "salestrack" (salestrack.db) at Fri Jul 29 2005
11:15

> Database "salestrack" (salestrack.db) started at Fri Jul 29 2005 11:15
> Starting checkpoint of "salestrack" (salestrack.db) at Fri Jul 29 2005
11:30

> Finished checkpoint of "salestrack" (salestrack.db) at Fri Jul 29 2005
11:30

> * * * ERROR * * * Assertion failed: 201848 (9.0.2.3044)
> Checkpoint log: write to \ Program Files\Sybase\ASA9\sa
lestrack.db failed
> with status 2: filesystem may be full
>
> Connection terminated abnormally
>
> Disconnected SharedMemory client's AppInfo: HOST=Pocket_PC;OS=Wi
ndows CE
3.0
> Build 11171; PID=0x93c94eba;THREA
D=0x92630b86;EXE=\Pr
ogram
>
Files\Sybase\ASA9\db
mlsync.exe;VERSION=9.0.2. 3044;API=DBLIB;TIMEZ
ONEADJUSTME
> NT=-300
>
> / * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
> * * * * * * /
>
> If during the synchronization process especially of the internal process
> that executes the pocket to ascend the it dates of the events donwload, we
> move the memory it works but that generates us complications that it
should
> always be been pending of the memory and if we neglect ourselves falls.
> In the pocket the error that usually comes out is the -301 that it means
> "Internal database error %1--transaction rolled back"
> Some way exists of overcoming this problem without necessity of being
moving
> the memory or that they recommend me
>
>
>

Luis Ponce Ibarra - Hotmail

2005-08-03, 8:24 pm

the empty database has 3.5 MB and the log 600 KB.
after synchronizing database has 12 MB and the log 7 MB.
exist other times that should be considered:
*5 MB when the program pocketbuilder that is used to synchronize rising
*to lift the database - dbsrv9 - 3 MB.
*the pocket has 64 MB and the remaining thing wastes away it the
synchronization.
*really where he/she wastes away the memory it is not the synchronization it
is later when you empiza to execute the download processes.

"Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
escribió en el mensaje news:42f0d1c7$1@foru
ms-2-dub...
> The log file and database file will need to grow while the download stream
> is being applied. If the device doesn't have enough memory to hold all
the
> information you want to send down, your either going to have to reduce the
> size of your downloads or increase the amount of space on the device.
>
> Exactly how large does the log file become when you download 40,000
records?
>
> --
> 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
>
> "Luis Ponce Ibarra - Hotmail" < luisponceibarra@hotm
ail.com> wrote in
message
> news:42ef9fac@forums
-1-dub...
> 3M
enough[color=darkred
]
> that
> normalemnte
*[color=darkred]
> *
Files\Sybase\ASA9\sa
lestrack.db)[color=darkred]
> 11:15
> 11:15
> 11:30
> 11:30
failed[color=darkred
]
> 3.0
>
Files\Sybase\ASA9\db
mlsync.exe;VERSION=9.0.2. 3044;API=DBLIB;TIMEZ
ONEADJUSTME
*[color=darkred]
> *
we[color=darkred]
> should
> moving
>
>

David Fishburn

2005-08-08, 9:24 am

"Luis Ponce Ibarra - Hotmail" < luisponceibarra@hotm
ail.com> wrote in
news:42f15ab6$1@foru
ms-1-dub of sybase.public.sqlanywhere.mobilink:

LPI-H> the empty database has 3.5 MB and the log 600 KB.
LPI-H> after synchronizing database has 12 MB and the log 7 MB.
LPI-H> exist other times that should be considered:
LPI-H> *5 MB when the program pocketbuilder that is used to synchronize
LPI-H> rising *to lift the database - dbsrv9 - 3 MB.
LPI-H> *the pocket has 64 MB and the remaining thing wastes away it the
LPI-H> synchronization.
LPI-H> *really where he/she wastes away the memory it is not the
LPI-H> synchronization it is later when you empiza to execute the
download
LPI-H> processes.

I see you are using VERSION=9.0.2.3044.

If you use a version that is > 902.3115 (so any of the current EBFs) it
will reuse the space inside the DB file to a much greater degree. This
should be of interest to you if you are tight on space.

The LOG file growth cannot be helped, which is why you would do
something like:

dbmlsync ... -os 3M
SET OPTION Public.Delete_old_logs = 'on'

You can read up on those two options/switches.

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