After Upgrade to 12c, AWR Host Memory is Incorrect with Solaris Zones
(Doc ID 2199537.1)
Last updated on FEBRUARY 21, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle 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
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- On 11.2 running on a Solaris zone with a 32 GB memory cap, AWR report shows correct host memory of 32GB ("Host Mem (MB)" and "Memory (GB)" values)
- After upgrade to 12c with no changes to the Solaris zone setup, the AWR report shows incorrectly 64GB as "Host Mem (MB)" and "Memory (GB)" values
i.e. basically the zone memory cap as defined in zonecfg:<zone-name>:capped-memory is being ignored and the total memory as seen in the global zone is being displayed.
- EM is showing correct 32GB (which is using a different OS interface altogether)
Changes
Upgrade from 11.2 to 12c on a NUMA hardware system (which is nowadays common type of hardware) with memory caps defined in the local Solaris zone.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |