I have SQL Anywhere 10 installed on an Arch Linux machine for development purposes. When I try to start a database server I now get an "out of memory" error. It worked fine up until a couple of days ago. What has changed since then is that I upgraded the linux kernel from version 2.6.* to 3.0.
This is the command I run:
This is the output I get:
My SA version: 10.0.1.4239
I have tried to set the cache sizes manually with the -c and -ca directives without success. The size of the database file is only about 25MB and I have 3G free memory.
We have not tested anything on the 3.0 kernel yet. We typically test on official releases of Linux distributions including Red Hat Enterprise, Suse, Ubuntu LTS, and Fedora. We probably will not officially support the 3.0 kernel until one of these distributions releases with it. We may never officially support the 3.0 kernel in SA 10.0.1, but we will try to be as helpful as we can.
The "Not enough memory" error indicates that the server failed to allocate a piece of memory that it needed. There could be lots of reasons for that. Calculating the cache size incorrectly (as you attempted to work around by specifying the cache size manually) could be just one of those.
SELinux, if that is enabled, could also cause such a problem. You could also check your
I cannot enumerate all possible reasons for this error.
If you run the server through
strace -o trace.out /opt/sqlanywhere10/bin64/dbsrv10 -n my_serv /path/to/database.db
Look in the resulting
If that doesn't show you anything useful, I would recommend that you work with technical support to send us some more diagnostic information.
This was probably caused by a bug in the way we compute system memory, as I alluded to in a comment in my other answer. I confirmed similar (but not exactly equivalent) behaviour using Fedora 16 with greater than 4GB of system memory.
I recorded this bug as CR 694479 and I have also fixed it. Since you are using version 10.0.1, you should look for a build number of at least 4311. Unfortunately, I don't know when the next 10.0.1 EBF is going to be released for Linux, but you can ask tech support if it's urgent.
As a work-around, if it's possible, you could remove some memory from your system. Get it below 4 GB if you can. I know 2 GB works well enough.
anyone has a workaround for this issue in ASA 9?
I have the same problem, but, ASA 9.
answered 07 Aug '12, 15:19