Skip to Content
Dec 28, 2020 at 08:10 AM

Memory allocation

55 Views Last edit Dec 28, 2020 at 08:32 AM 3 rev


In my system i have the limit of memory set as 150GB.

There is an procedure that actually returns error due to not being able to allocate enough memory.

I've found that if i ran this procedure in a debug mode then everything works fine, but when I try to run it as a standard procedure or function (for MAP_REDUCE) then I'm getting those errors, the same thing happens when I ran it as an anonymous block - if it's ran in debug mode then everything is fine, otherwise not.

As my understanding goes that can be caused by a parallel execution if there is an assignment, e.g.

short example:

lt_test = SELECT * FROM test_table;

lt_query2 = SELECT * FROM test_query q
JOIN :lt_test t 
ON =;

I'd like to ask if anyone could confirm that and it is caused because in debug mode it's ran in steps, where in normal mode it's ran in parallel.

Is there anything I can do with it?