My Oracle Support Banner

Use of the LIMIT parameter in Exadata IORM plan artificially throttles LGWR I/O (Doc ID 1562397.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Oracle Exadata Storage Server Software - Version to [Release 11.2]
Information in this document applies to any platform.


Incorrect over-throttling of LGWR I/O operations can be seen in Exadata with image version before, when IORM plan is in use and with the LIMIT parameter explicitly specified.

This is an example of such IORM plan:
CellCLI> alter iormplan
dbplan=((name=ORCL1, level=1, allocation=40, limit=40, flashcache=on),  -
(name=ORCL2,  level=1, allocation=40, limit=40, flashcache=on),  -
(name=ORCL3, level=1, allocation=15, flashcache=off),  -
(name=other, level=1, allocation=5, flashcache=off))


The issue may be observed after implementing or modifying an IORM plan in Exadata.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.