Database not using flashcache and IORM dbPlan is using profile
(Doc ID 2198539.1)
Last updated on APRIL 09, 2020
Applies to:Oracle Exadata Storage Server Software - Version 126.96.36.199.0 and later
Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
IORM interdatabase plans now support profiles that improve manageability of interdatabase plans for environments with many databases.
Minimum software: Exadata cell software release 184.108.40.206.0 running Oracle Database 12c Release 1 (12.1) release 220.127.116.11 Exadata Bundle Patch 4.
- Database performance is slow.
- AWR report shows "cell single block physical" Wait Avg & user/IO is high
- An inter-database IORM plan with profile directives is created on the cell.
- A database initialization parameter db_performance_profile is used as a requirement for use of IORM profiles see MOS Note - 1363188.1
AWR report shows Flash Cache Savings with little percentage on the Database Flash Cache but Cell usage is high:
Flash Cache Internal Reads also report no flashcache usage:
Upgraded to 18.104.22.168 Bundle Patch 4 or higher
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document