oracle shared memory error mesg.

[Sachin Soni_1]

i have a l2000 server with 2gb memory .
running 11.00

error mesg and o/p of top and glance is attached ,
can any one help me fast (:))


ORA-04031: unable to allocate 40976 bytes of shared memory ("large pool","unknow
n object","large pool hea","PX msg pool")

From TOP:

Memory: 758840K (93476K) real, 1224284K (74188K) virtual, 333360K free Page# 1/22

From Glance:

B3692A GlancePlus C.02.60.00 14:41:19 uwsnagw1 9000/800 Current Avg High
--------------------------------------------------------------------------------
CPU Util SSA AU | 9% 9% 9%
Disk Util FF | 4% 4% 4%
Mem Util S SU UB B | 84% 84% 84%
Swap Util R R | 48% 48% 48%
--------------------------------------------------------------------------------
MEMORY REPORT Users= 1
Event Current Cumulative Current Rate Cum Rate High Rate
--------------------------------------------------------------------------------
Page Faults 133 133 190.0 190.0 190.0
Page In 43 43 61.4 61.4 61.4
Page Out 0 0 0.0 0.0 0.0
KB Paged In 0kb 0kb 0.0 0.0 0.0
KB Paged Out 0kb 0kb 0.0 0.0 0.0
Reactivations 0 0 0.0 0.0 0.0
Deactivations 0 0 0.0 0.0 0.0
KB Deactivated 0kb 0kb 0.0 0.0 0.0
VM Reads 0 0 0.0 0.0 0.0
VM Writes 0 0 0.0 0.0 0.0

Total VM : 1.17gb Sys Mem : 136.9mb User Mem: 1.31gb Phys Mem: 2.00gb
Active VM: 1.06gb Buf Cache: 245.8mb Free Mem: 323.5mb
Page 1 of 1





thanks,
sachin

[Sanjay_6]

Hi Sachin,

Look like this should be for your DBA to look into. Don't think it is a system error ?.

Thanks

[Sachin Soni_1]

thanks sanjay

I am not much aware of database concept.
is there any kernel parameter , or anything i need to change.
or it is "just a oracle error"

thanks

[Sridhar Bhaskarla · Accepted solution]

OK Check the following..


> oerr ora 04031
04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s"
// *Cause: More shared memory is needed than was allocated in the shared
// pool.
// *Action: Either use the dbms_shared_pool package to pin large packages,
// reduce your use of shared memory, or increase the amount of
// available shared memory by increasing the value of the
// init.ora parameter "shared_pool_size".

So, the solution is clear. Go ahead and increase this parameter little bit more. Howerver, this is dependent on your shm_max size which is in turn dependent on the physical memory you have.


-Sri

[Sanjay_6]

Hi Sachin,

This is an oracle error, but let me see if i can suggest a solution, though i think it need to be implemented by your DBA.

Solution.

quote://

Cause: More shared pool is needed than was allocated in the shared pool

Solution: If the shared pool is out of memory, either use the dbms_shared_pool package to pin large packages, reduce your use of shared memory, or increase the amount os available shared memory by increasing the value of the INIT.ORA parameters "shared_pool_reserve_size" and shared_pool_size".
If the large pool is out of memory, increase the INIT.ORA parameter "large_pool_size".

//Endquote.

the init.ora file will be in $ORACLE_HOME/dbs directory

Hope this helps.

Thanks

[Varghese Mathew]

Hi Sachin,

Check the availability of shared memory in the machine using the #ipcs command, check out the man pages of ipcs..

Should be something related to Oracle only, u can probably hand over the issue to ur Oracle Admin.

Hope this helps..

Cheers !!!
Varghese Mathew

[Sachin Soni_1]

Hi All ,
thanks!

i got enough idea and working on this.
thanks a lot again.

:) ah varghese h r u buddy ? :)

[Varghese Mathew]

Hi Sachin,

Sorry folks something personal ..
my email id is vmathewk@yahoo.com, catch me there.

Cheers !!!
Varghese Mathew

[T G Manikandan]

Hello,
Just go into your $ORACLE_HOME/dbs directory.
OPen your init.ora file.
Increase your shared_pool_size value.
Restart your database.

THanks
G Manikandan

[Jayaprakash_1]

on what sequence you are receiving this error.here your problem was with large_pool_size.alter this parameter and restart the database.checkout the large objects in the shared pool using select * from
v$db_object_cache and keep those pl/sql object in the memory thru dbms_shared_pool.keep.

hope this helps.