The ORA-27102 error is generated on Solaris 10 having apparently correct settings of kernel parameters
(Doc ID 859898.1)
Last updated on NOVEMBER 27, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 9.2 to 11.2]
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 x86 (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
***Checked for relevance on 15-Dec-2016***
Someone wants to create one or more instances on a Solaris 10 box where the kernel parameters were set under that specific project as per Oracle Installation Guide and according to the following settings, some should be able to start a number of instances whose total SGA is : max-shm-memory * max-shm-ids.
Having the following settings:
project.max-shm-ids => 128
it results that up to 512 GB of shared memory could be allocated, but in reality only up to 4GB of shared memory for all instances belonging to a project can be allocated.
Trying to allocate more than 4GB of shared memory by increasing the SGA parameters will cause the occurrence of the "ORA-27102: out of memory" error.
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