A few things to note about Oracle 11.2 Instance access ASM:
1. The Oracle user and grid user must have the same group, and the ASM Disk's group is consistent with this group, otherwise the database cannot access ASM disks,
Error Ora 15081
For example: Both Oracle and Grid belong to the ASMDBA group, and the owner of the ASM disk is also ASMDBA
[[email protected] rules.d]# ID Oracle
UID=1001 (Oracle) gid=1000 (oinstall) groups=1000 (Oinstall), 1001 (DBA), 1002 (Oper), 1004 (ASMDBA)
[[email protected] rules.d]# ID grid
uid=1000 (GRID) gid=1000 (Oinstall) groups=1000 (Oinstall), 1001 (DBA), 1003 (asmadmin), 1004 (ASMDBA), 1005 (Asmoper)
[Email protected] rules.d]# ll/dev/sdb*
brw-rw-r--1 grid asmdba 8, Dec 13:44/dev/sdb
brw-rw-r--1 grid asmdba 8, Dec 17:58/dev/sdb1
brw-rw-r--1 grid asmdba 8, Dec 17:58/dev/sdb2
brw-rw-r--1 grid asmdba 8, Dec 17:58/dev/sdb3
brw-rw-r--1 grid asmdba 8, Dec 17:58/DEV/SDB4
2. $ORACLE _home/bin/oracle executable file is the correct owner should be oracle:asmadmin, and permissions must have s share to be able, as follows:
[Email Protected]:[/oracle/database/product/11.2.0/dbhome_1/bin] ll Oracle
-rwsr-s--x 1 Oracle asmadmin 232399473 DEC 14:51 Oracle
If the Oracle executable does not have the right permissions, you can execute the following command:
${gi_home}/bin/setasmgidwrap-o ${oracle_home}/bin/oracle
Check the permissions of the Oracle executable file after execution:
Ls-l ${oracle_home}/bin/oracle
This article is from the "Database Road" blog, make sure to keep this source http://dbaway.blog.51cto.com/7099215/1726376
Oracle 11.2 Single-instance connectivity ASM considerations and problem handling