Ora 27102 Linux Error 22
Contents |
: Fixing the 'ORA-27102: out of memory' Error By Giri Mandalika on Nov 21, 2008 (Crossposting the 2+ year old blog entry from my other blog hosted on blogger. ora-27102 out of memory linux Source URL: http://technopark02.blogspot.com/2006/09/solaris-10oracle-fixing-ora-27102-out.html) Symptom: As part of a database tuning effort you
Ora-27102 Out Of Memory Solaris 11
increase the SGA/PGA sizes; and Oracle greets with an ORA-27102: out of memory error message. The system had ora-27102 out of memory linux-x86_64 error 12 enough free memory to serve the needs of Oracle. SQL> startup ORA-27102: out of memory SVR4 Error: 22: Invalid argument Diagnosis $ oerr ORA 27102 27102, 00000, "out of memory" // \*Cause:
Ora-27102: Out Of Memory Solaris-amd64 Error: 22: Invalid Argument
Out of memory // \*Action: Consult the trace file for details Not so helpful. Let's look the alert log for some clues. % tail -2 alert.log WARNING: EINVAL creating segment of size 0x000000028a006000 fix shm parameters in /etc/system or equivalent Oracle is trying to create a 10G shared memory segment (depends on SGA/PGA sizes), but operating system (Solaris in this example) responded with ora-27102 out of memory windows an invalid argument (EINVAL) error message. There is a little hint about setting shm parameters in /etc/system. Prior to Solaris 10, shmsys:shminfo_shmmax parameter has to be set in /etc/system with maximum memory segment value that can be created. 8M is the default value on Solaris 9 and prior versions; where as 1/4th of the physical memory is the default on Solaris 10 and later. On a Solaris 10 (or later) system, it can be verified as shown below: % prtconf | grep Mem Memory size: 32760 Megabytes % id -p uid=59008(oracle) gid=10001(dba) projid=3(default) % prctl -n project.max-shm-memory -i project 3 project: 3: default NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory privileged 7.84GB - deny - system 16.0EB max deny - Now it is clear that the system is using the default value of 8G in this scenario, where as the application (Oracle) is trying to create a memory segment (10G) larger than 8G. Hence the failure. So, the solution is to configure the system with a value large enough for the shared segment being created, so Oracle succeeds in starting up the database instance. On Solaris
dba SQL*Plus: Release 10.2.0.3.0 - Production on Thu Aug
Ora-27102 Out Of Memory Oracle 11g
16 21:33:24 2012 Copyright (c) 1982, 2006, Oracle. All
Ora-27125 Solaris 12c
Rights Reserved. Connected to an idle instance. SQL> startup nomount pfile=/local/opt/oracle/product/10.2.0.3/db5/dbs/initDSP0001.ora ORA-27102: out ora-27125: unable to create shared memory segment solaris of memory Solaris-AMD64 Error: 22: Invalid argument Solution: *Solution:* This error represents that max-shm-memory is not sized correctly. Either reduce Oracle memory https://blogs.oracle.com/mandalika/entry/oracle_on_solaris_10_fixing usage on appropriate parameters. (OR) Increase max-shm-memory In increase max-shm-memory, run following command as root: Change the memory value based on your memory availability. root@xnodb916:~# prctl -n project.max-shm-memory -v 25gb -r -i project user.oracle root@xnodb916:~# prctl -n project.max-shm-memory -v 35gb -r -i project user.oracle Reducing https://manidba.wordpress.com/2012/08/16/oracle-startup-fails-with-ora-27102-out-of-memory-solaris-amd64-error-22-invalid-argument/ memory allocation on init***.ora fixed the issue. Reduced shared_pool_size, pga_aggregate_target and db_cache_size. Then started the DB successfully. SQL> startup nomount pfile=/local/opt/oracle/product/10.2.0.3/db5/dbs/initDSP0001.ora ORACLE instance started. Total System Global Area 1.2046E+10 bytes Fixed Size 2191376 bytes Variable Size 731680752 bytes Database Buffers 1.1308E+10 bytes Redo Buffers 4325376 bytes SQL> If AMM is enabled then SGA_TARGET and SGA_MAX_SIZE need to be reduced. Like this:Like Loading... Related Leave a Comment Leave a Comment » No comments yet. RSS feed for comments on this post. TrackBack URI Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are comment
of memory SVR4 Error: 22: Invalid argument HomeOracle DBAORA-27102: out of memory SVR4 Error: 22: Invalid argument I was trying to duplicate database using rman and it was erroring http://dbatalent.com/ora-27102-out-of-memory-svr4-error-22-invalid-argument-2/ out due to some issue. Post the issue, when I try to start the instance, I was getting: ORA-27102: out of memory SVR4 Error: 22: Invalid argument Details: DB - 11.2.0.4 Context - RMAN Duplication OS: Sun Solaris Sparc 11 When I 1st the error, I was thinking about: My Oracle Processes are running - But Instance was down and there is no oracle process running Top should show out of something - Nothing.. There weren't any Oracle Processes running Let me change Shared Memory Settings - /etc/system is not being used anymore in Solaris for shared memory segments. So you need to create profile. However even this also has not worked. You can see how to handle projects in my previous post : What Oracle DBA needs to know about Solairs - Projects Solution: I checked ipcs -a out of memory To my surprise I can see several shared memory segments and semaphores attached to oracle user even though there is no oracle processes running. Release the Shared Memory Segments by: ipcrm -m