startup nomount ORA-27100: shared memory realm already exists

最新推荐文章于 2021-05-25 17:31:32 发布

原创最新推荐文章于 2021-05-25 17:31:32 发布 · 1.5k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#service #windows #microsoft #database #server #parameters

本文解决了一个在启动Oracle数据库时遇到的ORA-27100错误问题，该错误通常发生在更改SGA大小并通过服务启动spfile之后。通过移动或重命名spfile并重启服务可以解决这一问题。

今天在qq群里一个哥们遇到了个问题。

紧急求救呀，
SQL> startup nomount pfile='d:/initbdmtst.ora';
ORA-27100: shared memory realm already exists

后来他自己找到了解决方案，

Ora-27100 even After Restarting the Windows Service [ID 370469.1]

我读完此文章后，我感觉此问题是32bit的os都有的问题，不管是windows的32bit 还是linux的32bit。不过此metalink文章里也没有说现象所在的os bit数是多少。

现在转帖出来：

Ora-27100 even After Restarting the Windows Service [ID 370469.1]

		修改时间 09-FEB-2010 类型 PROBLEM 状态 PUBLISHED

In this Document
  Symptoms
  Changes
  Cause
  Solution

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.6
z*OBSOLETE: Microsoft Windows Server 2003
***Checked for relevance on 09-Feb-2010***

Symptoms

Ora-27100 is reported during the startup of 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.

Changes

The parameter sga_max_size was changed from 2GB to 3GB through OEM.

Cause

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 an spfile.
When the service is restarted , it will use the spfile and the error occurs due to the SGA parameter change.

Solution

Move the spfile from it's default location or rename the spfile .
Restart the service.
Now the service will start the database using the pfile, with the old SGA settings.
This should allow successful startup of your database.

Create a new spfile from pfile.