Simpler Navigation coming for Servers and Operating Systems
Coming soon: a much simpler Servers and Operating Systems section of the Community. We will combine many of the older boards, and you won't have to click through so many levels to get at the information you need. If you are looking for an older board and do not find it, check the consolidated boards, as the posts are still there.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

Memory Allocation Error

abhay kumar_2
Occasional Contributor

Memory Allocation Error

We are running Sybase 11.9.3 on Digital Unix 4.0F.

We havea program failing continuously with "memory allocation error". When the program was running, the free memory falls gradually from 2 Gb to almost zero, and then the program fails.

The ulimit -a show the limit of data segment set to 2 Gb.

We can try increasing the limit, but it requires a reboot of production server and there is no guarantee that it will fix the problem.

Help urgently needed !!

abhay
3 REPLIES
Michael Schulte zur Sur
Honored Contributor

Re: Memory Allocation Error

Hi abhay,

I would assume, that this programme is allocating memory without releasing it. What programme is it?

greetings,

Michael

Re: Memory Allocation Error

You wrote "..free memory falls ... almost zero,"

How much you have a memory?

If the data segment size is almost same you get the trouble. You database software needs to use lot of physical memory but there must be also enough free physical memory to run OS, applications and small part of all users program.

Ilkka S
Ralf Puchner
Honored Contributor

Re: Memory Allocation Error

"memory allocation error" is mostly a problem of stack and data-size but depend also on the used functions/routines.

Databases normally allocates all statically memory using their own memory management. So the first thing to check is if the software vendor offers a tuning guide and to check the named parameters within this guides.

Maybe changing the swap-mode to lazy swap (removing /sbin/swapdefault and reboot) will also solve this problem - but this will be mentioned within the tuning guide.
Help() { FirstReadManual(urgently); Go_to_it;; }