Re: ORA-04030

Ah....let's increase the SHARED_POOL_SIZE first. If the problem still occurs, try to set SHARED_POOL_RESERVED_SIZE (check manual for correct parameter) in order to reserve enough continuous memory for your stored procedure or other database object.

Billy Verreynne wrote:

> The error:
> ORA-04030: out of process memory when trying to allocate 320 bytes (cursor work
> he,kdiixs1 : kdipc)
>
> oerr says:
> 04030, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)"
> // *Cause: Operating system process private memory has been exhausted
> // *Action: [none specified]
>
> The platform:
> Oracle 8.1.5
> HP-UX B.11
>
> What seems a bit strange to me is that this happens on a SQL SELECT/JOIN which
> is not as massive as the other ones I have experimented with (populating a
> warehouse). I have run a 44 million join (1 VLT, 2 smaller tables) without a
> problem. Now I am doing a 1 million row join (1 VLT and 5 smaller tables) and it
> fails. This join is actually pretty fast.. SQL results from this join are being
> delivered by Oracle before it goes belly up with the ora-04030 error. This is
> also unlike the long running jobs where you do not get any results before Oracle
> packs up with a temp space problem or the like.
>
> I have asked Unix admin to look into this, but no comments from them at this
> time.
>
> Any ideas?
>
> --
> Billy
Received on Mon Sep 17 2001 - 11:13:06 CDT