OPF Out of Memory

: Hello,
:
: We've started using a new version of our software to the production
: system. It has been completely tested on test server before. And now on
: some selects we recieve 'E_OP0002 optimizer run out of memory before
: generating execution plan'. If I delete some conditions from where
: clause then all goes fine. I can not find what parameter should I
: increase in Ingres configuration on production server. Please, help!!!
: Our system is stopped now.
:
: Thanks in advance,
: Nick
:
: P.S. We are using OI 1.2/00 (rmx.us5/01) with patch 3953.
:
:

Normally, these errors caused by too many OR or AND clauses. Like what
Martin said, increase the opf.memory parameter via CBF. Another thing to
note is that: OI 1.2/00 is too buggy, try move to OI 1.2/01 with the
appropriate patches.

Ciao,
Lawrence Choy
Ingres + Internet Consultant (Malaysia)
Alternate Address:
lschoy@email.com

________________________________

----- Original Message -----
From: Nick Dobrovolski 
To: Ingres Conference 
Sent: Wednesday, May 19, 1999 05:42
Subject: EMERGENCY: E_OP0002 optimizer run out of memory

Martin Bowes wrote:

> Hi Nick,
>
>     In CBF.
>
>     Enter the Configure DBMS Server Definition screen and select the Derived
>     parameters option. You need to alter up the 'opf_memory' or reduce
>     opf_active_limit.
>
>     eg. I normally run with opf_memory=9000000 and opf_active_limit=5
>     This is suitable for my installations yours of course may vary wildly form
>     this.
>
>     Having altered these parameters, you will have to restart the servers.
>
>     Martin Bowes



Hello!

Many thanks to all of you, especially to Martin Bowes. He gave me the magic
figures. :-))) Before sending this letter I of course played with opf_memory in
cbf. I increased it 2, 4, 8 times but the query still failed. After setting both
parameters to suggested values all went fine. As I can see OI uses 200 Kb of
optimizer memory per session (opf_memory=6400000 and opf_active_limit=32). While
setting it to 1.8 Mb all goes fine. As I can see I missed only one step while
doubling opf_memory in my previous investigations (51200000/32=1600000). :-)))
There was lack of only 200Kb per session. Bewitched number. :-)))

Again thanks to all of you.

Regards,
Nick
Ingres Q & A
Back to William's Home Page
Email William