DISM Process not Disabled After Setting SGA_TARGET Equal to SGA_MAX_SIZE and Unsetting MEMORY_TARGET and MEMORY_MAX_TARGET in RAC Environment
(Doc ID 2024253.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Solaris on SPARC (64-bit)
It has been observed that the oradism process is still enabled on a RAC database environment, even though SGA_TARGET and SGA_MAX_SIZE are equal and both MEMORY_TARGET and MEMORY_MAX_TARGET are set to zero, so DISM is not used.
This document explains the possible reason and how can you ensure that the memory allocations are not DISM.
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