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.

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.

What version and build of SQL Anywhere are you using?


Scott Blauert wrote:

We're using version 11.0.1.2308 of SQL Anywhere.

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

Scott Blauert wrote:

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.

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


Scott Blauert wrote:

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.

If you need any additional information, e-mail me at
sblauert (AT) lanl (DOT) gov. Thanks for the help.

Sorry, I wanted to add to this thread:
http://groups.google.com/group/sybas...646afc7d81c2b7
but the "Reply" option has been turned off for it.

I'm running version 11.0.1.2376 and we're still seeing this error when
attempting db connect on some of our devices.
I have set the cache size in the connection string and that does seem
to clear the problem.
However we would really like Ultralite to figure out the ideal cache
size for us, as the dbs vary in size from time to time and device to
device.
Is Change Request 557818 still considered closed?
Just wanted to make sure before I jump into writing my own cache-size-
calculator algorithm, and at the very least give you guys a heads up
that 557818 may not actually be entirely resolved.

Thanks!
Dave