ITPub博客

首页 > 数据库 > Oracle > Startup Instance Failed with ORA-27140 ORA-27300

Startup Instance Failed with ORA-27140 ORA-27300

Oracle 作者:Curry_0316 时间:2015-12-17 15:13:15 0 删除 编辑
文章转自MOS:
Startup Instance Failed with ORA-27140 ORA-27300 ORA-27301 ORA-27302 and ORA-27303 on skgpwinit6 (文档 ID 1274030.1)

APPLIES TO:

Oracle Database - Standard Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 29-Mar-2013*** 

SYMPTOMS

On : 11.2.0.1 version, Real Application Cluster

When attempting to start database as oracle user, the following errors are seen in alert log.

ERROR
-----------------------

ORA-00210: cannot open control file
ORA-00202: error in writing''+RECODG/utsdb/controlfile/current.256.732754521''
ORA-17503: ksfdopn: 2 Failed to open file +RECODG/utsdb/controlfile/current.256.732754521
ORA-15001: diskgroup "RECODG" does not exist or is not mounted
ORA-15055: unable to connect to ASM instance
ORA-27140: attach to post/wait facility failed
ORA-27300: OS system dependent operation:invalid_euid failed with status: 1
ORA-27301: OS failure message: Not owner
ORA-27302: failure occurred at: skgpwinit5
ORA-27303: additional information: startup euid = 100 (grid), current euid = 101 (oracle)



STEPS
-----------------------
The issue can be reproduced at will with the following steps:

$ sqlplus "/as sysdba"
SQL> startup


Or in some cases, DBCA fails to create database with :

ORA-19503:failed to create file +OLTP
ORA-15001: disk group does not exist or is not mounted
ORA-15055: Unable to connect to ASM instance

ORA-27140:attach to post/wait facility failed
ORA-27300: OS system dependent operation: invalid_egid failed with status 1
ORA-27301: OS failure message:operation not permitted
ORA-27302: failure occured at: skgpwinit6
ORA-27303: additional information: startup egid = 501(oinstal),current egid=502(dba)

 

CAUSE

The issue is caused by wrong permission of the GI_HOME/bin/oracle executable.

In one case, customer changed the file permission of GI_HOME/bin/oracle from "-rwsr-s--x" to "-rwxrwxr-x".
The correct permission should be "-rwsr-s--x".

SOLUTION

1. Stop the CRS.
2. Change the file permission of GI_HOME/bin/oracle to "-rwsr-s--x":

$su - grid
$cd GI_HOME/bin
$chmod 6751 oracle
$ls -l oracle


3.Start the /CRS.

4.Test if you can startup the rdbms database using oracle user.

5. For issue in DBCA, Re-run DBCA.

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/29953799/viewspace-1873968/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2014-10-11

  • 博文量
    86
  • 访问量
    244329