Re: Alert Log Errors!

Found something related on technet FAQ. It seems my java_pool_size is too small.

If you run out of memory while compiling (within loadjava or deployejb), you should see an error: A SQL exception occurred while compiling:

   : ORA-04031: unable to allocate bytes of shared memory   ("shared pool","unknown object","joxlod: init h",   "JOX: ioc_allocate_pal")

The cure is to shut down your database and to reset JAVA_POOL_SIZE to a larger value. The mention of "shared pool" in the error message is a misleading reference

Buck Turgidson <jc_buck_at_YAH00.com> wrote in message news:f%936.5028$aI6.360988_at_bgtnsc05-news.ops.worldnet.att.net...
> I am consistently getting messages in the alert log, apparently having to do with memory. Is this anything I need to act upon?
 The
> database comes up, albeit in a very small SGA. This is a development instance. The java_shared_pool is 4194304.
>
> ORA-00604: error occurred at recursive SQL level 1
> ORA-04031: unable to allocate 4032 bytes of shared memory ("shared pool","unknown object","joxlod: in ehe","ioc_allocate_pal")
> ORA-06512: at "SYS.DBMS_JAVA", line 0
> ORA-06512: at line 2
> Fri Dec 29 19:28:39 2000
> Completed: alter database open
>
>
> SVRMGR> startup
> ORACLE instance started.
> Total System Global Area 8736752 bytes
> Fixed Size 69616 bytes
> Variable Size 6950912 bytes
> Database Buffers 1638400 bytes
> Redo Buffers 77824 bytes
> Database mounted.
> Database opened.
>
>
Received on Fri Dec 29 2000 - 18:49:42 CST