Database Memory & 4030/4031 (MOSC)

MOSC Banner

need some explanation

edited Oct 8, 2009 2:41AM in Database Memory & 4030/4031 (MOSC) 2 commentsAnswered

On some databases we can not start the database with more than 6000 processes and receive ORA-64. We tried the workaround in bug 5959853, it works. But we need some more explanation:
1. All our databases do not have sga_max_size set. We have set db_cache_size and shared_pool_size big enough.
2. We have similar cache sizes  on our databases from some GB, so our granule size is allways 16 MB.
3. Some of the databases can be started with 8000 processes, some can not.

So, the explanation to the ORA-64 on startup is, that oracle needs to write the session array in one granule (= one contiguous chunk) in the SGA. But our granule size  is allways 16 MB. So why can oracle write the session array for 8000 sessions in one granule on some databases and on others it can not. Can you please explain this?

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