Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 
 

ORA-27100: shared memory realm already exists tips

Oracle Error Tips by Stephanie F.

 

The Oracle docs note this on the ora-27100 error:

ORA-27100: shared memory realm already exists
 
Cause: Tried to start duplicate instances, or tried to restart an instance that had not been properly shutdown
 
Action: Use a different instance name, or cleanup the failed instance"s SGA

Also see Startup Fails With ORA-27100 After Restarting The Windows Service [MOSC ID 370469.1]

Typically, ORA-27100 can be resolved by simply restarting Windows.  However, Internet sources offer advice for times when this error is thrown, and not easily resolved, applying to Oracle Enterprise; version 9.2.0.6.0 and Microsoft Server 2003.  The error may be thrown similarly to the example below upon starting up the database:

startup nomount
ORA-27100: shared memory realm already exists

SQL> shutdown immediate
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist

Restarted the service , still the same error.
Rebooting the server did not help as well.

This is caused by

  • The parameter sga_max_size was changed from 2GB to 3GB through OEM.
  • Changing the parameter from OEM will make the change in the spfile.
  • ORA-27100 is received as a result of changes made to parameters affecting the SGA size.
  • The service was created to start with spfile .
  • When the service is restarted , it will use the spfile and the error occurs due to SGA parameter change.

To resolve ORA-27100, you should execute the following instructions:

- Move the spfile from its default location or rename the spfile .

- Restart the service

- Now the service will start the database using pfile , with old SGA settings.  This should start your database successfully .

- Create the new spfile from pfile.


 

 

  
 

 
 
 
 
 

 
 
 
 
 
 
Oracle training Excel
 
Oracle performance tuning software 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright ? 1996 -  2014

All rights reserved by Burleson

Oracle ? is the registered trademark of Oracle Corporation.


Hit Counter