Precautions and troubleshooting for connecting a single Oracle 11.2 instance to ASM

Precautions and troubleshooting for connecting a single Oracle 11.2 instance to ASM

Notes for accessing ASM from an Oracle 11.2 instance:

1. Oracle users and grid users must have the same group, and the ASM Disk group must be consistent with this group. Otherwise, the database cannot access the ASM Disk, and the ora 15081 error is returned.

For example, oracle and grid both belong to the asmdba group, and the owner of the asm disk is also asmdba.

[Root @ host rules. d] # id oracle

Uid = 1001 (oracle) gid = 1000 (oinstall) groups = 1000 (oinstall), 1001 (dba), 1002 (region), 1004 (asmdba)

[Root @ host rules. d] # id grid

Uid = 1000 (grid) gid = 1000 (oinstall) groups = 1000 (oinstall), 1001 (dba), 1003 (asmadmin), 1004 (asmdba), 1005 (asmoper)

[Root @ host rules. d] # ll/dev/sdb *

Brw-rw-r -- 1 grid asmdba 8, 16 Dec 19 13:44/dev/sdb

Brw-rw-r -- 1 grid asmdba 8, 17 Dec 19 17:58/dev/sdb1

Brw-rw-r -- 1 grid asmdba 8, 18 Dec 19 17:58/dev/sdb2

Brw-rw-r -- 1 grid asmdba 8, 19 Dec 19 17:58/dev/sdb3

Brw-rw-r -- 1 grid asmdba 8, 20 Dec 19 17:58/dev/sdb4

2. The correct owner of $ ORACLE_HOME/bin/oracle executable file should be oracle: asmadmin, and the permission must be shared by s, as shown below:

Oracle @ host: [/oracle/database/product/11.2.0/dbhome_1/bin] ll oracle

-Rwsr-s -- x 1 oracle asmadmin 232399473 Dec 19 14:51 oracle

If the oracle executable file permission is incorrect, run the following command:

$ {GI_HOME}/bin/setasmgidwrap-o $ {ORACLE_HOME}/bin/oracle

After the execution is complete, check the oracle executable file permissions:

Ls-l $ {ORACLE_HOME}/bin/oracle