Startup Nomount Fails With ORA-27123 If SGA Size >=1250GB And SGA_TARGET UNSET
(Doc ID 1945197.1)
Last updated on FEBRUARY 24, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.4 [Release 11.2]Oracle Solaris on SPARC (64-bit)
Symptoms
Startup nomount nails with ORA-27123 if SGA size >=1250GB and SGA_TARGET is unset (SGA is sized manually) on Oracle Solaris SPARC 64-bit
SQL> startup nomount
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 7
Additional information: 50331746
Additional information: 0
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 7
Additional information: 50331746
Additional information: 0
Pool and buffer sizes are set like below:
*.log_buffer=76136448
stgeds2.db_16k_cache_size=900G
stgeds2.db_cache_size=250G
stgeds2.db_keep_cache_size=100G
stgeds2.shared_pool_size=18G
stgeds2.streams_pool_size=1G
stgeds2.java_pool_size=1G
stgeds2.large_pool_size=1G
stgeds2.db_16k_cache_size=900G
stgeds2.db_cache_size=250G
stgeds2.db_keep_cache_size=100G
stgeds2.shared_pool_size=18G
stgeds2.streams_pool_size=1G
stgeds2.java_pool_size=1G
stgeds2.large_pool_size=1G
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 |