Ora 27102 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. Source URL: http://technopark02.blogspot.com/2006/09/solaris-10oracle-fixing-ora-27102-out.html) Symptom: As part of a ora-27102 out of memory solaris 11 database tuning effort you increase the SGA/PGA sizes; and Oracle greets with an ORA-27102: out of memory error message. The system had enough free memory to serve the needs of Oracle. SQL> startup ORA-27102:
Ora-27102 Out Of Memory Solaris 10
out of memory SVR4 Error: 22: Invalid argument Diagnosis $ oerr ORA 27102 27102, 00000, "out of memory" // \*Cause: Out of memory // \*Action: Consult the trace file for details Not so helpful. Let's look
Ora-27102: Out Of Memory Solaris-amd64 Error: 22: Invalid Argument
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 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 ora-27102 out of memory linux-x86_64 error 12 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 9 and prior releases, it can be done by adding the following line to /etc/system, followed by a reboot for the system to pick up the new value. set shminfo_shmmax = 0x000000028a006000 However shminfo_shmmax parameter was obsoleted with the release of Solaris 10; and Sun doesn't recommend setting
and
Ora-27102 Out Of Memory Windows
SafetyAsset NetworkAsset Operations and MaintenanceCommerceOverviewSubscription Billing ora-27102 out of memory oracle 11g and Revenue ManagementMaster Data Management for CommerceOmnichannel CommerceFinanceOverviewAccounting and ora-27125 solaris 12c Financial CloseCollaborative Finance OperationsEnterprise Risk and ComplianceFinancial Planning and AnalysisTreasury and Financial Risk ManagementHuman ResourcesOverviewCore https://blogs.oracle.com/mandalika/entry/oracle_on_solaris_10_fixing Human Resources and PayrollHuman Capital AnalyticsTalent ManagementTime and Attendance ManagementManufacturingOverviewManufacturing NetworkManufacturing OperationsResponsive ManufacturingMarketingOverviewMarket with Speed and AgilityUnique Customer ExperiencesReal-Time Customer InsightsR&D/EngineeringOverviewDesign NetworkDesign OrchestrationProject and Portfolio ManagementSalesOverviewCollaborative Quote to CashSales Force AutomationSales https://scn.sap.com/thread/946027 Performance ManagementSelling Through Contact CentersServiceOverviewEfficient Field Service ManagementOmnichannel Customer ServiceTransparent Service Process and OperationsSourcing and ProcurementOverviewContingent Workforce ManagementDirect ProcurementSelf-Service ProcurementServices ProcurementStrategic Sourcing and Supplier ManagementSupply ChainOverviewDemand ManagementDemand NetworkLogistics NetworkManufacturing Planning and SchedulingResponse NetworkResponse and Supply ManagementSales, Inventory, and Operations PlanningTransportation ManagementWarehouse ManagementSustainabilityOverviewEnvironment, Health, and SafetyProduct Safety and Stewardship NetworkBrowse by IndustryAerospace and DefenseAutomotiveBankingChemicalsConsumer ProductsDefense and SecurityEngineering, Construction, and OperationsHealthcareHigh TechHigher Education and ResearchIndustrial Machinery and ComponentsInsuranceLife SciencesMediaMill ProductsMiningOil and GasProfessional ServicesPublic SectorRetailSports and EntertainmentTelecommunicationsTravel and TransportationUtilitiesWholesale DistributionBrowse Platform and TechnologyAnalyticsOverviewBusiness IntelligencePredictive AnalyticsGovernance, Risk, and ComplianceEnterprise Performance ManagementApplication Platform and InfrastructureOverviewApplication
dba SQL*Plus: Release 10.2.0.3.0 - Production on Thu Aug 16 21:33:24 2012 Copyright (c) 1982, 2006, Oracle. All Rights Reserved. Connected to an idle instance. https://manidba.wordpress.com/2012/08/16/oracle-startup-fails-with-ora-27102-out-of-memory-solaris-amd64-error-22-invalid-argument/ SQL> startup nomount pfile=/local/opt/oracle/product/10.2.0.3/db5/dbs/initDSP0001.ora ORA-27102: out 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 usage on http://www.dbasupport.com/forums/showthread.php?7461-ORA-27102-out-of-memory 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 out of -i project user.oracle root@xnodb916:~# prctl -n project.max-shm-memory -v 35gb -r -i project user.oracle Reducing 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 out of memory 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 commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. PagesAbout simple ways to stay fresh middle of theday Blogroll Documentation Plugins Suggest Ideas Support Forum Themes WordPress Blog WordPress Planet Categories: Database Keepalived MySQL Backup Upgrade Xtrabackup Oracle ASM Backup Dataguard Data Guard Broker Enterprise Manager RAC RMAN Project Management Thought of the day Toastmasters Uncategorized Search: Archives: June 2015 May 2015 March 2015 December 2013 September 2013 April 2013 March 2013 January 2013 December 2012 November 2
of memory If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 7 of 7 Thread: ORA-27102: out of memory Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 03-01-2001,04:51 PM #1 ora_inf View Profile View Forum Posts Member Join Date Jan 2001 Posts 230 I trying to create the database and I am getting the following error........ ====================================================== sun_Unix> svrmgrl Oracle Server Manager Release 3.0.5.0.0 - Production (c) Copyright 1997, Oracle Corporation. All Rights Reserved. Oracle8 Enterprise Edition Release 8.0.5.0.0 - Production PL/SQL Release 8.0.5.0.0 - Production SVRMGR> connect internal Connected. SVRMGR> @crdb_ORACLE_SID.sql Connected. ORA-27102: out of memory SVR4 Error: 22: Invalid argument create database "ORACLE_SID" * ORA-01034: ORACLE not available Disconnected. =========================================================== Thanks Reply With Quote 03-01-2001,05:08 PM #2 ramk_vv View Profile View Forum Posts Junior Member Join Date Feb 2001 Posts 17 Hi, I suspect some problem with shared memory or semaphore parameters in /etc/System file.Either they are set too high or not set properly.It's just a guess. Ramki Reply With Quote 03-01-2001,05:17 PM #3 marist89 View Profile View Forum Posts Visit Homepage Super-Genius Join Date Nov 2000 Location greenwich.ct.us Posts 9,092 That's where I would start looking, /etc/system... Jeff Hunter marist89@yahoo.com http://marist89.blogspot.com/ "I pledge to stop eating sharks fin soup and will not do so under any circumstances." Reply With Quote 03-01-2001,05:18 PM #4 Halo View Profile View Forum Posts Moderator Join Date Apr 2000 Location Edison, NJ Posts 759 Do not allocate more than 1/2 the RAM available on the server for the instance(s). Check settings in /etc/system also. Reply With Quote 03-01-2001,05:59 PM #5 ora_inf View Profile View Forum Posts Member Join Date Jan 2001 Posts 230 Hi: You guys are right Following parameter was not set in /etc/system file so I have requested sys. admin to make this change. After he make the changes then I will try again Thanks lot..... ============================= set semsys:seminfo_semmni=5200 set semsys:seminfo_semmns=8000 set semsys:seminfo_semmnu