Re: Catpatch.sql Problem

Daniel,

the patchset notes have explicit requirement of at least 150megs for both shared_pool_size and java_pool_size (Java VM and XML DB Requirements section.) No reqs on soft session space limit, so I think you don't need to change this (I've got a bunch of warnings for soft session space limit being exceeded in trace file when applying the patch, but no crashes.) And I think that java_pool_size can be safely reduced to about 50 megs after the patch is applied (I left mine at 60 megs and it's working fine.)

hth.

--
Vladimir Zakharychev (bob@dpsp-yes.com)                http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.


"DA Morgan" <damorgan_at_exxesolutions.com> wrote in message
news:3E755D98.4D7673A3_at_exxesolutions.com...


> Finally I've got a problem I can't solve.

>

> Just patched from 9.2.0.1.0 to 9.2.0.2 and now it is time to run

> catpatch.sql on a 500MB PIII running W2K. And here's the error message

>

> DOC>#######################################################################

>

> DOC>#######################################################################

>

> DOC> The following statement may cause an

> DOC> ORA-29554: unhandled Java out of memory condition

> DOC> error, and thereby terminate the sqlplus connection.

> DOC> If so, this is because there is insufficient system tablespace,

> DOC> shared or java pool size, or some other resource value is too

> small.

> DOC> An additional message describing the problem will be output by

> DOC> the statement.

> DOC>#######################################################################

>

> DOC>#######################################################################

>

> DOC*/

> BEGIN initjvmmaux.check_sizes_for_cjs; END;

>

> *

> ERROR at line 1:

> ORA-29554: unhandled Java out of memory condition

> ORA-06512 at "SYS.INITJVMAUX", line 167

> ORA-06512 at line 1

>

> And yes I've checked the google archives and yes I've run all over otn

> and tahiti and metalink. And I will tell you for free the information at

> metalink is so bad Oracle should hang its head in shame. Lots of

> statements about what the problem is ... not a single solution.

>

> Ive done shutdown followed by startup migrate numerous times and it

> seems that no setting for the following:

>

> java_pool_size=51200000

> java_soft_sessionspace_limit=10240000

>

> solves the problem. These are my current values.

>

> Has anyone done this successfully and could you please post the init

> parameters that made it work. If not these ... which ones?

>

> Thanks,

>

> Daniel Morgan

>