An example of ASM disk not found in DBCA Library

  • Environmental Information
    red hat linux64 
    gi 11.2.0.4 
    oracle 11.2.0.4
  • Problem Phenomena
    After installing gi software and oralce database software, the database is built through the dbca user interface. It is found that the database can be built normally on node1, not on node2. The dbca library building process errors on node2.
    Figure:

  • View disk group status on node1 and node2

node1:
su - grid
SQL> select name,state from v$asm_diskgroup;

NAME                           STATE
------------------------------ -----------
SYSDG                          MOUNTED
DATADG                         MOUNTED
node2:
SQL> select name,state from v$asm_diskgroup;

NAME                           STATE
------------------------------ -----------
SYSDG                          MOUNTED
DATADG                         MOUNTED
//View through the asmcmd command, you can see the files inside the asm disk group normally 
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • View dbca log and oraagent_as shown by screenshot errorOracle.log(
    dbca log
    /app/oracle/cfgtoollogs/dbca/RAC 
    /app/grid/11.2.0/log/rac2/agent/crsd/oraagent_oracle
[Thread-200] [ 2016-09-07 16:29:32.180 CST ] [DatabaseImpl.crsResource:3608]  calling parent's crsResource
[Thread-200] [ 2016-09-07 16:29:32.931 CST ] [PostDBCreationStep.executeImpl:885]  Starting Database HA Resource
[Thread-200] [ 2016-09-07 16:30:24.426 CST ] [CRSNative.internalStartResource:389]  Failed to start resource: Name: ora.rac.db, node: null, filter: null, msg CRS-5017: The resource action "ora.rac.db start" encountered the following error:
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DATADG/RAC/spfileRAC.ora'
ORA-17503: ksfdopn:2 Failed to open file +DATADG/RAC/spfileRAC.ora
ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 13: Permission denied
Additional information: 26
Additional information: 196613
. For details refer to "(:CLSN00107:)" in "/app/grid/11.2.0/log/rac2/agent/crsd/oraagent_oracle/oraagent_oracle.log".

CRS-2674: Start of 'ora.rac.db' on 'rac2' failed
CRS-2632: There are no more servers to try to place resource 'ora.rac.db' on that would satisfy its placement policy
[Thread-200] [ 2016-09-07 16:30:24.427 CST ] [PostDBCreationStep.executeImpl:893]  Exception while Starting with HA Database Resource PRCR-1079 : Failed to start resource ora.rac.db
CRS-5017: The resource action "ora.rac.db start" encountered the following error:
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DATADG/RAC/spfileRAC.ora'   Tips are inaccessible spfile file
ORA-17503: ksfdopn:2 Failed to open file +DATADG/RAC/spfileRAC.ora
ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 13: Permission denied
Additional information: 26
Additional information: 196613
. For details refer to "(:CLSN00107:)" in "/app/grid/11.2.0/log/rac2/agent/crsd/oraagent_oracle/oraagent_oracle.log".

CRS-2674: Start of 'ora.rac.db' on 'rac2' failed
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28

Log hints can't access spfile files, but it's weird to find them in the disk group by grid users.(
So think about why:
dbca establishes the database as an oracle user operation, while the grid user manages the disk group. The obvious phenomenon is that the oracle user cannot read or access the files of the asm disk group on node 2, so this problem may occur

  • Verify this idea further
    Attempting dbca to set up database on node2 found asm disk group + DATADG not found when selecting data file storage path

  • At this point, the problem is clear, oracle cannot find asm disk groups
    View oracle user permissions for two nodes:

node1 :
id oracle
uid=501(oracle) gid=5001(oinstall) group=5001(oinstall),5002(dba),5003(oper),5006(asmdba)
node2:
uid=501(oracle) gid=5001(oinstall) group=5001(oinstall),5002(dba),5003(oper),5006(asmdba)
  • 1
  • 2
  • 3
  • 4
  • 5

View GRID_HOME and oracle_Permissions for oracle files in the bin directory of HOME:

node1:
cd $GRID_HOME/bin
ls -l oracle
-rwsr-s--x 1 grid oinstall 209914519 9month   7 14:40 oracle   File permissions are correct
node2:
ls -lrt oralce
-rwxr-x--x 1 grid oinstall 209914519 9month   7 14:42 oracle   File permission error
oracle User:
cd $ORACLE_HOME/bin
ls -l oracle
node1:
-rwsr-s--x 1 oracle asmadmin 239626689 9month   7 15:56 oracle  Correct
node2:
-rwsr-s--x 1 oracle asmadmin 239626689 9month   7 16:04 oracle  Correct
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14

The question is clear:
In node2, GRID_Error oracle file permissions in HOME/bin directory
Modify:
chmod +s oracle 
Returning to the DBCA library building interface to continue execution will successfully discover the ASM disk group and build the library.

Tags: Oracle Database SQL Linux

Posted on Sun, 05 Jul 2020 11:45:40 -0400 by dannybrazil