Database Administration (MOSC)

MOSC Banner

How do the granule size and sub pools affect the resizing of memory in Oracle 11gr2 database?

edited Nov 19, 2014 10:00AM in Database Administration (MOSC) 2 commentsAnswered

We are on Oracle database version 11.2.0.3 with Automatic Shared Memory Management(ASMM) enabled. It is a RAC database with 2 instances. The memory target is 55G and SGA target is currently 38G. All other ameters i.e. shared_pool_size,db_cache_size,java_pool_size,large_pool_size,streams_pool_size have been set to 0.

Also, due to legacy reasone, we have the parameter *._kghdsidx_count=1 which we forgot to remove.

The current configuration includes 20 CPU's per instance and a granule size of 128M.

The issue we are facing is that the dynamic memory resizing does not takes place as it always shows 'Cancelled' in the status column of the view v$memory_resize_ops. It is unable to grow/shrink memory between shared pool and database buffer cache. 

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center