Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Give Feedback...
ORA-27102: Out of Memory During Startup on Solaris10 Server with Multiple DB Instances Owned by Multiple To Bottom
Users (Doc ID 1931165.1)
Symptoms Yes
No
Changes
Cause
Document Details
Solution
References
Type:
PROBLEM
Status:
PUBLISHED
Last Major
APPLIES TO: Update:
03-Dec-2014
03-Dec-2014
Last Update:
Oracle Database - Enterprise Edition - Version 9.2.0.4 to 11.2.0.4 [Release 9.2 to 11.2]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit) Related Products
Oracle Database - Enterprise
SYMPTOMS Edition
All instances of the server are up and running except this one.
Document References
No References available for
CHANGES this document.
Multiple instances exist in the database server and owned by different OS users. Recently Viewed
Total physical memory of the server is greater than the sum of the SGA of all instances. 11.2:./RUNINSTALLER
results in: Could not execute
auto check for display colors
'project.max-shm-memory' parameter is set for all the OS users owning an instance and this value is greater than the SGA of the
using command
corresponding instance. /usr/bin/xdpyinfo [888699.1]
11gR1 OUI will not proceed
CAUSE without the xdpyinfo
command [747645.1]
Solaris Cluster HA-SAP
The error ORA-27102 is thrown when the instance is being started, eventhough free memory is available on the server and SGA ORCL.sapstartsrv Resource
of this instance is smaller than 'project.max-shm-memory' parameter value set for this OS user owning this instance. Starts Replicated Enqueue
Server even When
The reason for the error is that this instance has not released shared memory and semaphores with an earlier database ORCL.saprepenq Resource is
Offline [2228664.1]
shutdown.
How to repair a zpool that
remains in a DEGRADED
SOLUTION state despite there being no
current or recent errors
[1636482.1]
Determine which instance owns which shared memory segment and which semaphore Amount Unreconciled In
Report Shows Incorrect
SQL> oradebug setmypid Balance For Foreign
Currency Lines [264715.1]
SQL> oradebug ipc Show More
The shared memory segment id can be found by looking in the trace file for Shmid.
The semaphore id can be found by looking in the trace file for Semaphore List=
Then remove the shared memory segment(s) and semaphore(s) of the problematic instance by using following commands:
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=436787924512574&parent=EXTERNAL_SEARCH&sourceId=PROBLEM&id=1931165.1&_a
4/12/2018 Document 1931165.1
After removing the remaining shared memory segment(s) and semaphores of the probematic instance, start the instance as
normal.
NOTE:
The specified interprocess communication API kernel entities are marked for removal, deferred until the last connected
process detaches.
Please refer to the ipcrm manual pages.
Related
Products
Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Enterprise Edition > RDBMS > Common errors like ORA-27102 / server process
memory leaks / server process memory usage / swapping
Back to Top
Copyright (c) 2018, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=436787924512574&parent=EXTERNAL_SEARCH&sourceId=PROBLEM&id=1931165.1&_a