I was running a price list update session and part way through I got a BW Error message saying Warning - Low on Memory. This was backed up with the following line in the bshell log.

Log_mesg: WARNING: Running low on memory

What memory is this message referring to server or client side?

Thanks

PJ

Hi,

I think that refers to the servers memory.

Remember: A bshell process allways run on the server. The client just gives you a view on it.

Is it a selfmade Session?

In this case check how often you do a commit.

Doing a single commit after updating lots of datas often causes problems because baan (or the DBMS) must store to much transactions during the procedure.

You need to check on the memory statistics using -


Print memory usage to file and show file being used:
bshcmd6.2 -m -l <bshell_pid>

or

check the swap/system/reserved memory using the

Glance tools, or top command.

OK

I've ran some further testing on this problem. On the same server and same Baan system I can run the same update session in four other companies and I do not receive any 'Low on Memory' errors.

This would indicate to me that system memory/swap space resources are sufficiently set on our server.

I have confirmed that the session script commits one record at a time there is no large rollback created.

Is there anything else that you can suggest needs looking at.

Thanks

PJ

Hi Pj,

We have the same error by session Update Cost prices (ticpr2220m000) .
The session runs over 3 days and we are getting the error .

I found some solution suggestions on bgs You can find it in the attached file .

hope this will help you .

We haven't solve our problem yet . If you will solve it please let me know.



Caner

Thanks for your reply Caner,

I too have been given the same documents by BGS

I don't think our issue is related to memory as we can run the same session in other Baan issues without errors.

Regards

PJ

Hi PJ,
When a session is running for a long duration of time and it exceeds the process size maintained for the system, it aborts with this error.
Probably you would also have got an error /* Display Server Termination or likes */

Run a session and monitor the process size using top or similar tools. Compare the size of process when it aborts with the process size maintained

I guess this should be it......

Hi,

I've had the same problem while running a specific session.
Generate GRP orders).
The session got looping, because some data of one record was not consistent.
After changing the data, the problem had been solved and no error of: running low/out of memory.
Is it possible to do a dbs.log on that session, so that you are able to retrieve the record, which the seesion is trying to update?
Then take a look for the data, if it is correct.

GN