Base out of memory

Can anyone point me in the right direction here

2 users in a room of 32 users.
Design a table - name, DOB, phone number etc  no images or the like
Table saves OK
When you try and enter data it says

SQL Staus : S1000
Error code: 72
out of memory

Machines are openSUSE 13.2
8G ram

Ta

M

Hi :slight_smile:
I am not sure about the SQL error code and haven't even looked it up
yet. However it does sound like a quite small database that shouldn't
be having any trouble with memory.

As a quick first try maybe radically increasing the default settings
in LibreOffice might help.
Tools - Options - Memory
The defaults are all for MUCH lower spec machines so you can easily
allow LibreOffice to use much larger amounts of Ram. Hmm, all the
settings seem to be about graphics and objects so i'm not sure it
would help. I think it's still worth a try though.

Regards from
Tom :slight_smile:

The error comes up before you have really had a chance to enter any data
If you enter the first row and then start entering data in the second row the 
error pops as soon as the cursor goes to the first field in the second row.

Mal

Hi :slight_smile:
I have just found this old thread;
https://forum.openoffice.org/en/forum/viewtopic.php?f=13&t=19016
and it might well still be very relevant. Also this thread;
http://listarchives.libreoffice.org/global/users/msg08764.html

Err, do you know if you are using an external back-end to contain the
data? If you are not sure then you are probably using the internal
back-end so that the whole database appears to be just 1 file. Base
is much better when the tables are exported into an external back-end
that Base then just links to. The internal back-end is just to help
those who are more familiar with MS's "Access" but Base is far more
powerful, thanks to it's ability to connect with a wide variety of
external back-ends. Something small fast and powerful such as HSqlDb
might be ideal for your use-case even though it's built on Java;
http://hsqldb.org/
An ancient, heavily tweaked and very restricted form of HSqlDb was
squeezed into being the back-end for Base and there has been some work
into switching to a newer and more easily updateable internal back-end
but i am not sure about the progress. Anyway the proper full releases
of HSqlDb perform much better than the internal version.

Sorry i am not being very helpful here! Hopefully someone with a lot
more understanding and/or knowledge will appear or someone give some
other ideas worth trying.

Regards from
Tom :slight_smile:

The message points to a lack of assigned memory for the Java VM process
that launches the Base-hdslqdb combination. Could it be that the
machines in question are using multiple other Java threads or apps and
there is not enough memory left to allocate to the opened ODB Java
hsqldb instance ?

If you want to increase the allocated Java resources for an ODB file,
you have to extract it, and go and tweak one of the database specific
configuration files contained therein (unfortunately, can't remember
which one, possibly SCRIPT.

The message could also be completely erroneous or misleading, such
things have already happened in LibreOffice, but then finding out what
really is the problem will be more difficult.