Database Will Not Mount: ORA-15025, ORA-27041, 'Permission denied', ORA-15081 (Doc ID 1378747.1)

Last updated on JUNE 27, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
Checked relevance on 19-Aug-2014

Symptoms

Database instance will not mount:

alert_ORCL.log:
~~~~~~~~~~~~~~~~~~
...
Thu Nov 17 14:32:28 2011
Starting ORACLE instance (normal)
...
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options.
...
Thu Nov 17 14:32:33 2011
ALTER DATABASE MOUNT
NOTE: Loaded library: System
ORA-15025: could not open disk '/dev/oracleasm/disks/DATA01'
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9

SUCCESS: diskgroup DATA was mounted
NOTE: dependency between database ORCL and diskgroup resource ora.DATA.dg is established
ORA-15025: could not open disk '/dev/oracleasm/disks/FLASH01'
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9

SUCCESS: diskgroup FLASH was mounted
ORA-00204: error in reading (block 1, # blocks 1) of control file
ORA-00202: control file: '+FLASH/orcl/controlfile/current.256.711293457'
ORA-15081: failed to submit an I/O operation to a disk
ORA-00204: error in reading (block 1, # blocks 1) of control file
ORA-00202: control file: '+DATA/orcl/controlfile/current.256.711293457'
ORA-15081: failed to submit an I/O operation to a disk
NOTE: dependency between database ORCL and diskgroup resource ora.FLASH.dg is established
Thu Nov 17 14:32:36 2011
Checker run found 2 new persistent data failures
ORA-205 signalled during: ALTER DATABASE MOUNT...
Sat Nov 19 02:51:01 2011
SUCCESS: diskgroup DATA was dismounted
SUCCESS: diskgroup FLASH was dismounted


The ASM instance has all necessary ASM diskgroups mounted.


Changes

Job role separation between the ASM and the Database software owners, check fine (see exception further below):

The ASM software owner has proper Primary Group, ASM OSASM, ASM OSDBA, ASM OSPER and Database OSDBA groups assigned to it:

# id grid
uid=27637(grid) gid=7101(oinstall) groups=106(dba),787(asmadmin),788(asmdba),789(asmoper),7101(oinstall)

The Database software owner has proper Primary Group, Database OSDBA, Database OPER, and ASM OSDBA groups assigned to it:

# id oracle
uid=19114(oracle) gid=7101(oinstall) groups=106(dba),786(oper),788(asmdba),7101(oinstall)

The ASM disks have the proper user:group and file permissions:

# ls -ltra /dev/oracleasm/disks/*
brw-rw---- 1 grid asmadmin 8, 161 Nov 19 05:08 /dev/oracleasm/disks/DATA01
brw-rw---- 1 grid asmadmin 8, 177 Nov 19 05:08 /dev/oracleasm/disks/FLASH01

Proper SETUID (SETGID), owner for each of the Oracle Homes' oracle executable:

-rwsr-s--x 1 grid oinstall 184437523 Sep 13 2010 /appl/oraasm/OracleHomes/asm_1/bin/oracle
-rwsr-s--x 1 oracle oinstall 210973186 May 31 21:25 /appl/oracle/OracleHomes/11.2.0/bin/oracle

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms