1825793 Members
2894 Online
109687 Solutions
New Discussion

Monk error

 
SOLVED
Go to solution
MarkW_1
Regular Advisor

Monk error

I have a user working with an interface application on an L class box OS 11.0 getting the following error:

18:37:46 __MONKFILE=`table.dgt_dgt/table.dgt.mfl'
FAILURE: new_MONK_atom() -- calloc(1000, 88) failed [strerror(12)=(Not enough sp
ace)]

>>Dynamic Evaluation Of Internal Data
>>>>ERR: MONK_object_create_pair: call to new_MONK_atom() Failed. Probable Syst
em Memory Allocation Problem.
>>>>ERR: load: .
>>>>ERR: load: .
18:38:18 loaded:`/home/dgtest2/tables/table.dgt'

5 REPLIES 5
harry d brown jr
Honored Contributor

Re: Monk error

Mark,

You probably need to jack up maxdsiz. What's the current value?

live free or die
harry
Live Free or Die
MarkW_1
Regular Advisor

Re: Monk error

harry,

maxdsiz 67108864
maxssiz 67108864

Mark
A. Clay Stephenson
Acclaimed Contributor

Re: Monk error

Hi:

Errno 12 = ENOMEM. You almost certainly need to increase maxdsiz. Maxssiz will not cause a failure of calloc(). A reasonable increase would be to 128MB or 256MB. If you have a large amount of RAM, you could go higher still. You might be running out of virtual memory so check your amount of swap space but I suspect that increasing maxdsiz is all you need.
If it ain't broke, I can fix that.
MarkW_1
Regular Advisor

Re: Monk error

Here is swaoinfo:

swapinfo
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 2097152 82188 2014964 4% 0 - 1 /dev/vg00/lvol2
localfs 2848768 0 2848768 0% none 0 1 /usr1/paging
reserve - 506004 -506004
memory 749156 533000 216156 71%
#
A. Clay Stephenson
Acclaimed Contributor
Solution

Re: Monk error

Hi Mark:

You seem to have quite a bit of swap so that should not be your problem. By the way, if this is a 64-bit application then you need to set maxdsize_64bit because maxdsiz applies to 32-bit applications. In any event, increase them to fix your problem.
If it ain't broke, I can fix that.