cancel
Showing results for 
Search instead for 
Did you mean: 

7.6.06.03: POS(1) No more memory

Former Member
0 Kudos

We are using the instance profile parameter

dbs/ada/input_parameters = 10000

(according to Note 655018 - Input parameters for SQL statements increased)

to enable users to do bigger selections. This works fine but in a few cases where the system dumps with

Fehlertext der Datenbank...: "POS(1) No more memory"
Interne Aufrufcodierung....: "[RSQL/OPEN/MARA ]"

What kind of "memory" is here referred to?

7.6.06.03

Linux x86_64

Markus

Accepted Solutions (1)

Accepted Solutions (1)

former_member185954
Active Contributor
0 Kudos

Hello Markus,

I googled this error and found that this could be related to unavailability of sufficient cache memory.

http://lists.mysql.com/maxdb/19648

Regards,

Siddhesh

markus_doehr2
Active Contributor
0 Kudos

Hi Siddhesh,

thank you for you answer.

That instance has has CACHE_SIZE of 4,500,000 = 36 GB of memory. This should be sufficient to execute that query

Markus

former_member185954
Active Contributor
0 Kudos

Ah,

Maybe it points to some component within that 36GB cache. But I am assuming you must have done that research already

Regards,

Siddhesh

markus_doehr2
Active Contributor
0 Kudos

This error is occurring since we enabled that 10.000 parameter input limit (instead of 2000) so I assume, there are other workprocess local buffers which don't have enough memory to do something - depending on the width of the table to be read. Some tables work fine, others do not.

Markus

lbreddemann
Active Contributor
0 Kudos

Hi Markus,

I updated the message.

Looks like there is too few memory to prepare a multi-table-join statement with >9500 bind variables and OR concatenations.

Let's move over the discussion to the support message and update this thread when we know what's going on, OK?

regards,

Lars

Answers (2)

Answers (2)

markus_doehr2
Active Contributor
0 Kudos

Thank you Lars - done so (657272 2009).

lbreddemann
Active Contributor
0 Kudos

Hello Markus,

please open a support message for this error.

thanks,

Lars