WARNING: "oradism not set up correctly", When Setting SGA_MAX_SIZE
(Doc ID 374367.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.4 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Symptoms
On Solaris platform, after enabling Automatic SGA Management (ASMM) and setting SGA_MAX_SIZE, when restarting the database, an oradism warning appears in the alert log.
The instance starts and the shared_pool_size can be changed with an alter system command.
Symptoms can also include higher kernel cpu usage.
Changes
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 |