Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Dynamic Memory Exhausted Error

258 views
Skip to first unread message

scottblauert

unread,
Jan 25, 2010, 6:53:41 PM1/25/10
to
Hello,

We recently added quite a bit of data to our database and
now we get the "Dynamic Memory Exhausted" error when our
application attempts to open the connection to the UltraLite
database from the .NET code (ULConnection class, Open()
method).

We think this is strange since our Windows Mobile devices
have 67 MB of program memory free and 140 MB of storage
memory free. The database is a total of 22 MB.

Is it truly the case that our devices are running out of
memory or could the error be caused by something else?

Thanks for your help.

scottblauert

unread,
Jan 25, 2010, 7:42:43 PM1/25/10
to
Another interesting bit is that the application is useable
after initial synchronization as long as the application is
not closed. It's when the application is restarted and the
Open method called that the error occurs.

Kory Hodgson (Sybase iAnywhere)

unread,
Jan 26, 2010, 9:15:58 AM1/26/10
to
What version and build of SQL Anywhere are you using?

scottblauert

unread,
Jan 26, 2010, 10:05:24 AM1/26/10
to
We're using version 11.0.1.2308 of SQL Anywhere.

Chris Keating (Sybase iAnywhere)

unread,
Jan 26, 2010, 10:20:23 AM1/26/10
to
Are the UL components also that same version? Do you specify CACHE_SIZE
as part of your connection parameters? Can you add CACHE_SIZE=5M and see
whether that changes the behaviour.

-chris

scottblauert

unread,
Jan 26, 2010, 10:45:06 AM1/26/10
to
No, I was not specifying the CACHE_SIZE as part of the
connection parameters, but when I added CACHE_SIZE=5m, it
solved the problem.

Chris Keating (Sybase iAnywhere)

unread,
Jan 26, 2010, 11:07:35 AM1/26/10
to
This is likely related to Engineering Case#557818.

Can you confirm the version and build of UL.Net that you are using (look
at the assembly and ulnet11 library versions that you are deploying to
the device.

-chris

scottblauert

unread,
Jan 26, 2010, 11:19:17 AM1/26/10
to
The ulnet11.dll we deploy to the devices is version
11.0.1.2308 and the UL db was built using the 2308 version
of ulinit, although I have had to tweak the schema since
then using Sybase Central.

scottblauert

unread,
Jan 26, 2010, 12:14:03 PM1/26/10
to
If you need any additional information, e-mail me at
sbla...@lanl.gov. Thanks for the help.

Omar

unread,
May 5, 2011, 1:35:52 PM5/5/11
to
We are experiencing the exact same issue on WM5 device. The version on the deployed ulnet11.dll file is: 11.0.0.1612.
According to case # 557818 - http://search.sybase.com/kbx/changerequests?bug_id=557818, this should have been fixed in 11.0.0.1611.

I have tried setting the Cache Size to 5M, 4M, 2M and still experience this issue from time to time.
What is the 'appropriate value' that cache size needs to be set to? or is there another workaround?

Thanks for your help.

0 new messages