Home » RDBMS Server » Server Administration » Why shared pool exceeds after startup ?
Why shared pool exceeds after startup ? [message #59548] Wed, 03 December 2003 01:49 Go to next message
sachin kumar gupta
Messages: 157
Registered: March 2003
Senior Member
Hi all,
My question is when I fix my SGA parameters like (shared pool size, java pool size, large pool size etc.) in spfile_SID.ora. Then after starting up the database why the fixed SGA parameters exceed the configured ones(mostly the shared pool exceeding around 200 MB). I haven't modified these parameters dynamically.

TIA,
Sachin
Re: Why shared pool exceeds after startup ? [message #59551 is a reply to message #59548] Wed, 03 December 2003 05:34 Go to previous messageGo to next message
jagjeet singh
Messages: 16
Registered: October 2001
Junior Member
hi,
I Think your database is not using spfile which one you are providing.

And there is no Underscore "_" in naming convention.

Try this

startup spfile= PATH_of_File
Re: Why shared pool exceeds after startup ? [message #59552 is a reply to message #59548] Wed, 03 December 2003 05:45 Go to previous messageGo to next message
Thiru
Messages: 1089
Registered: May 2002
Senior Member
Sachin,
Are you talking about the difference between init.ora parameter shared_pool_size and size reported by v$sgastat ?

For eg)
thiru@9.2.0:SQL>show parameter shared_pool_size

NAME TYPE VALUE
------------------------------------ ----------- ---------
shared_pool_size big integer 33554432

thiru@9.2.0:SQL>select sum(bytes) from V$sgastat where pool like 'shared pool%';

SUM(BYTES)
----------
50331648

They are different becos 'shared_pool_size' is a contributor to the overall size of the shared pool,not the 'only' contributor. There are so many other components in the shared pool like process arrays,controlfile entries,session entries etc that take up 'space' that is not included in the 'shared_pool_size' parameter.

Besides,from 9i onwards, Oracle rounds up the value you specify to the nearest granule size,the size of which varies based on your total sga size etc.

For eg)
thiru@9.2.0:SQL>select * from V$SGA_DYNAMIC_COMPONENTS;

COMPONENT CURRENT_SIZE MIN_SIZE MAX_SIZE OPER_COUNT LAST_O LAST_O
---------------------------------------------------------------- ------------ ---------- ---------- ---------- ------ ------
LAST_OPER GRANULE_SIZE
--------- ------------
shared pool 33554432 33554432 33554432 0
4194304

large pool 16777216 16777216 16777216 0
4194304

buffer cache 41943040 41943040 41943040 0
4194304

It shows a granule size of 4MB for my SGA.

Hope this clarifies
Thiru
Re: Why shared pool exceeds after startup ? [message #59558 is a reply to message #59552] Wed, 03 December 2003 20:53 Go to previous messageGo to next message
sachin kumar gupta
Messages: 157
Registered: March 2003
Senior Member
That's what I wanted to know. Thanx a lot.
I have one more question for u:
Is it possible to automate the db startup (not through OEM) using spfile. I know spfile is a binary file, that's why I was unable to startup using startup command & oradim? Is there any way?
TIA,
Sachin
Re: Why shared pool exceeds after startup ? [message #59568 is a reply to message #59558] Thu, 04 December 2003 04:23 Go to previous message
Thiru
Messages: 1089
Registered: May 2002
Senior Member
Sure. Just have your spfile in your $ORACLE_HOME/database/spfileORACLE_SID.ora and use control_panel-->Services to enable auto start .

-Thiru
Previous Topic: how to fix internal error code -600 at database level
Next Topic: how to fix internal error code -600 at database level
Goto Forum:
  


Current Time: Fri Sep 20 08:23:27 CDT 2024