Database Memory & 4030/4031 (MOSC)

MOSC Banner

ORA-4031 after enabling Dynamic SGA

edited Oct 8, 2009 2:29AM in Database Memory & 4030/4031 (MOSC) 5 commentsAnswered
 Getting "ORA-04031: unable to allocate 4064 bytes of shared memory ("shared pool","lock table sys.mon_mods$ in ...","sga heap(1,0)","kglsim heap")" after enabling SGA_TARGET. Oracle 10.2.0.2/AIX 5.3

Old SGA Setting:

*.sga_max_size=1948225392
*.shared_pool_size=939524096
*.shared_pool_reserved_size=92776955
*.java_pool_size=67108864
*.large_pool_size=8388608
*.streams_pool_size=50331648
*.db_cache_size=939524096


Enabled dynamic SGA by adding SGA_TARGET and retaining the other *pool size for the minimum allocation: Only Changes in the spfile were:
*.sga_max_size=1936M
*.sga_target=1936M

After the above change, 30 minutes into a client copy we started receiving ORA-4031 and the DB was in accessible. I had to abort the database.

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