WARNING: "oradism not set up correctly", When Setting SGA_MAX_SIZE
Last updated on APRIL 07, 2015
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
***Checked for relevance on 07-Apr-2015***
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms