Exadata General (MOSC)

MOSC Banner

How to control or measure impact of IORM plan on redo apply process?

in Exadata General (MOSC) Question

We have large warehouse Oracle Database RAC database running on two Exadata X9.
DB version: 19.24
ESS version: 23.1.18.0.0

Production runs on first exadata - no problem here.
On second Exadata we have 2 vm clusters. On one there ADG standby running. On second there are 3 dev/test databases - these 2 clusters do not share CPU but they share Exadata Storage servers.

We struggle to correctly prioritze (or measure) I/O related to redo apply process over I/O requests comming from dev/test databases. Normally we use high_throughput with db plan per unique name - but we tried "auto" policy too. Even if we set shares=20 for ADG Standby and shares=3 for each dev/test database - we sometimes experience situation in which redo apply process is lagging for long time which we can be only resolved by stopping some of dev/test databases. Just because stopping workload from databases running on different vm cluster helps - makes us think the problem is related with I/O

Tagged:

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