Re: Please help - ORA 04030: out of process memory...

"Henry" <henry_2303_at_hotmail.com> wrote in message news:<hJqDa.350257$w7k.193583_at_news04.bloor.is.net.cable.rogers.com>...
> Paul,
>
> Thanks. I did not find any notes in the readme file about the minimum size
> od shared_pool_size for the upgrade in the readme file of the 8.1.7.2.1
> patch. But I believe the minimum size is about 52MB (at least that was
> minimum for the installation).
> I tried also 150MB but it did not helped.
>
> Also the "select * from duc$ where PACK='JIS$INTERCEPTOR$';" and subsequent
> delete they added only in 8.1.7.3 version. I'm not sure if I should do it
> also for the older patch...(?)
>
> FYI, patching to the 8.1.7.3 works fine on the same hardware and same init
> file setting. I'n just having lots of problems with this 8.1.7.2.x version.
> Unfortunately this one is certified and has to be used...
>
> Regards,
> Henry

Henry,

Was there any chance that you were relying on large memory support (/3GB boot option)? That worked for us (W2K Advanced Server, 4 GB physical memory) with 8.1.7.3.0 - I don't think that we used it prior to that patchset. It did not work for us in the 8.1.7.4.x patchsets.

If your SGA is sized very large - the amount of memory counts against the virtual memory - whether of not it is "committed" (in the OS). Could you try reducing the value for db_block_buffers for the rebuild so that your total SGA would be under 1 GB?

Paul

>
>
> "Paul Drake" <drak0nian_at_yahoo.com> wrote in message
> news:1ac7c7b3.0306031454.65138f7c_at_posting.google.com...
> > "Henry" <henry_2303_at_hotmail.com> wrote in message
> news:<k73Da.121909$cK1.102755_at_news01.bloor.is.net.cable.rogers.com>...
> > > Hi,
> > >
> > > I'm getting this error (ORA 04030: out of process memory...) when I
> tried to
> > > upgrade existing 8.1.7 database to 8.1.7.2.1 and also when I tried to
> create
> > > new instance after I upgraded the server the server to 8.1.7.2.1.
> > >
> > > In the upgrade if fails during the catproc.sql. Few objects were invalid
> > > after the script but I was able to recompile/rebuild most of them.
> > > The one remained invalid - SYS.DBMS_PRVTAQIS. I have got the ORA 04030
> again
> > > when i tried to run prvtaquis.plb to recreate this package
> individualy...
> > >
> > > During the new instance creation with database assistant I got the same
> > > error when addind plsql support - so it probably related to the same
> problem
> > > as in the first case...
> > >
> > > I tried to patch the server to 8.1.7.2.7 but it did not helped for this
> > > case.
> > >
> > > I'm running Win 2000 on Pentium III 600MHz with 384MB Ram and the
> pagefile
> > > growed to 1.6GB during this steps.
> > > I tried to install the same thing Pentium IV with 512MB RAM but same
> > > thing... so it does not seem to be a lack of resources but rather some
> leak
> > > in Oracle...
> > >
> > > I'm thinking to to try higher version of Oracle but Application we are
> using
> > > is certified to 8.1.7.2 so I would rather avoid that.
> > >
> > > Does anyone has similar experience or have any suggestions how to
> proceed ?
> > >
> > > Thanks a lot,
> > > Henry
> >
> > Henry,
> >
> > Please re-read the readme.htm for the patchset carefully.
> > In that doc - it mentions that you must set the java_pool_size to a
> > minimum value for the rebuild of the java machine to succeed - and it
> > may mention a minimum size for the shared pool while rebuilding the
> > dictionary.
> >
> > In any event, there are several steps you need to perform while
> > patching.
> > I prefer to use a separate init.ora file that has the following
> > parameters set:
> > (this is all covered in detail in the readme.htm)
> >
> > job_queue_processes=0
> > _system_trig_enabled=false
> >
> > you also must pay attention to:
> >
> > select * from duc$ where PACK='JIS$INTERCEPTOR$';
> >
> >
> > for applying the patchset 9.2.0.3 - the recommended pool sizes are 150
> > MB.
> >
> > hth,
> >
> > Paul
Received on Wed Jun 04 2003 - 18:41:05 CDT