Database Memory & 4030/4031 (MOSC)

MOSC Banner

ASMM, v$sga_resize_ops and shared pool issues

edited Oct 8, 2009 2:09AM in Database Memory & 4030/4031 (MOSC) 6 commentsAnswered
I have a 9 year old database with multiple applications in it that don't use bind variables.  Hence, I have a big and busy shared pool.  The database has been handling it okay until today when we put more load on it than usual.  I know we need to use bind variables but that will take some time.  We also have some poor SQL that causes a load on the buffer cache.  Again, the database (ASMM and MMAN) seems to have handled this until today.

Prior to today, I would see new rows in v$sga_resize_ops all the time - mman was working hard by constantly shrinking and growing both the shared pool and buffer cache.  Since 10/31 (today is 11/3) no new rows have been added.  However, I still see updated data in v$sga_dynamic_components and the mman trace file was being updated.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center