Re: PL/SQL procedures won't fit in memory

Hi,

Had run into the same problem with Oracle 7.2.3 on Solaris 2.5. The interesting part is that when I tried to pin the procedure using the dbms_spool package I got the same error (this was done after executing the alter system flush shared_pool command, performing a check point and switching the log file). The shared_pool_size was 21Mb and I got an error "unable to allocate 740 bytes...". When I listed the sizes of all the objects in the shared_pool (using the dbms_spool package) it totalled to 3 MB only.

The error vanished after I restarted the instance. Expecting a logical explanation to this problem. Please email.

Thanks for any help.

Naren
nchintala_at_worldnet.att.net

youngpa_at_statcan.ca (Paul Young) wrote:
>
>We've been using PL/SQL more and more in our application development.
>I believe we've hit some kind of limit though. We have some fairly large
>procedures and sometimes they just don't run. Sometimes they do.
>
>It seems that when the system is busier, they fail. The error I receive
>is:
>
> DECLARE
> *
> ERROR at line 1:
> ORA-04031: unable to allocate 86184 bytes of shared memory ("IMP_RE_FVAR1","PL/S
> QL MPCODE","BAMIMA: Grow Bam Buffer")
> ORA-06508: PL/SQL: could not find program unit being called
> ORA-06512: at line 93
>
>Oracle Versions on HP Unix UX10:
> Oracle7 Server Release 7.1.6.2.0 - Production Release
> PL/SQL Release 2.1.6.2.0 - Production
>
>Have you ever received and worked around this problem. Please E-mail a
>response. Many thanks in advance.
>
>
>PGY (Opinions expressed are mine and mine alone)
>################################################################
># Paul Young #
># youngpa_at_statcan.ca #
># Statistics Canada #
>################################################################
Received on Sun Jul 21 1996 - 00:00:00 CEST