Database Administration (MOSC)

MOSC Banner

what could be impact to set _rollback_segment_count to 30,000?

edited Jun 26, 2012 6:42PM in Database Administration (MOSC) 4 comments
One database was set _rollback_segment_count = 15,000 in 10G, after 11G upgrade, oracle put 10G rollback segment offline and create 15,000 online rollback segment for 11G. Now offline rollback segment cause high latch contention(row cache objects) when run large amount parallel query. THe only workaround from Oracle support is to convert all 10G offline rollback segments to 11G and bring all online. That solution will have database to run 30K rollback segments.

THe questions are:

Anyone have experience to run 30K rollback segments.

What can be the negtive impact/overhead to have 30K RB online.

What could be the protential risk to have 30K RB in 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

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