My Oracle Support Banner

ORA-15072 during Root.sh On Second Node. (Doc ID 2520819.1)

Last updated on JANUARY 06, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Linux x86-64

Symptoms

In two node RAC 11.2.0.4

Root.sh succeeded on node 1 and failed on node 2 with below error message.

 

[root@<host2> ~]#<GRID_HOME>/root.sh
Performing root user operation for Oracle 11g
The following environment variables are set as:
  ORACLE_OWNER= grid
  ORACLE_HOME=<grid_home>
Enter the full pathname of the local bin directory: [/usr/local/bin]:
  Copying dbhome to /usr/local/bin ...
  Copying oraenv to /usr/local/bin ...
  Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: <grid_home>/crs/install/crsconfig_params
Creating trace directory
User ignored Prerequisites during installation
Installing Trace File Analyzer
OLR initialization - successful
Adding Clusterware entries to oracle-ohasd.service
CRS-2672: Attempting to start 'ora.mdnsd' on '<node2>'
CRS-2676: Start of 'ora.mdnsd' on '<node2>' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on '<node2>'
CRS-2676: Start of 'ora.gpnpd' on '<node2>' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on '<node2>'
CRS-2672: Attempting to start 'ora.gipcd' on '<node2>'
CRS-2676: Start of 'ora.cssdmonitor' on '<node2>' succeeded
CRS-2676: Start of 'ora.gipcd' on '<node2>' succeeded
CRS-2672: Attempting to start 'ora.cssd' on '<node2>'
CRS-2672: Attempting to start 'ora.diskmon' on '<node2>'
CRS-2676: Start of 'ora.diskmon' on '<node2>' succeeded
CRS-2676: Start of 'ora.cssd' on '<node2>' succeeded
Disk Group CRS creation failed with the following message:   >>>>>>>>>>>>>>>>>>
ORA-15018: diskgroup cannot be created   >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
ORA-15072: command requires at least 1 regular failure groups, discovered only 0
ORA-15080: synchronous I/O operation to a disk failed
Configuration of ASM ... failed
see asmca logs at /u01/app/grid/cfgtoollogs/asmca for details
Did not succssfully configure and start ASM at <ORACLE_BASE>

 

[root@<node1> ~]# ls -lrt /dev/oracleasm/disks
total 0
brw-rw---- 1 grid asmadmin 249, 6 Mar 17 05:57 CRS1
brw-rw---- 1 grid asmadmin 249, 7 Mar 17 05:57 CRS2
brw-rw---- 1 grid asmadmin 249, 8 Mar 17 05:57 CRS3
brw-rw---- 1 grid asmadmin 249, 9 Mar 17 05:57 DATA1
brw-rw---- 1 grid asmadmin 249, 10 Mar 17 05:57 DATA2
brw-rw---- 1 grid asmadmin 249, 11 Mar 17 05:57 FRA1

[root@<node2> ~]# ls -lrt /dev/oracleasm/disks
total 0
brw-rw---- 1 grid asmadmin 8, 16 Mar 17 06:01 CRS1
brw-rw---- 1 grid asmadmin 8, 32 Mar 17 06:01 CRS2
brw-rw---- 1 grid asmadmin 8, 48 Mar 17 06:01 CRS3
brw-rw---- 1 grid asmadmin 8, 64 Mar 17 06:01 DATA1
brw-rw---- 1 grid asmadmin 8, 80 Mar 17 06:01 DATA2
brw-rw---- 1 grid asmadmin 8, 96 Mar 17 06:01 FRA1

 

/etc/sysconfig/oracleasm  >> This file having correct entry in BOTH nodes.

=============

# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="dm"

# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE="sd"

==============

 

NODE 1:
=====
[root@<node1> ~]# /etc/init.d/oracleasm querydisk -d CRS1
Disk "CRS1" is a valid ASM disk on device [249,6]
[root@<node1> ~]# /etc/init.d/oracleasm listdisks | xargs /etc/init.d/oracleasm querydisk -p
Disk "CRS1" is a valid ASM disk
/dev/mapper/crs1p1: LABEL="CRS1" TYPE="oracleasm" >>>>>>>>>>>>>>>>>>>>>>>>>/dev/mapper/crs1p1
Disk "CRS2" is a valid ASM disk
/dev/mapper/crs2p1: LABEL="CRS2" TYPE="oracleasm"
Disk "CRS3" is a valid ASM disk
/dev/mapper/crs3p1: LABEL="CRS3" TYPE="oracleasm"
Disk "DATA1" is a valid ASM disk
/dev/mapper/data1p1: LABEL="DATA1" TYPE="oracleasm"
Disk "DATA2" is a valid ASM disk
/dev/mapper/data2p1: LABEL="DATA2" TYPE="oracleasm"
Disk "FRA1" is a valid ASM disk
/dev/mapper/fra1p1: LABEL="FRA1" TYPE="oracleasm"

NODE2:
=====
[root@<node2> ~]# /etc/init.d/oracleasm querydisk -d CRS1
Disk "CRS1" is a valid ASM disk on device [8,16]
[root@<node2> ~]# /etc/init.d/oracleasm listdisks | xargs /etc/init.d/oracleasm querydisk -p
Disk "CRS1" is a valid ASM disk
/dev/sdb: LABEL="CRS1" TYPE="oracleasm" >>>>>>>>>>>>>>>>>>>>>>>>>/dev/sdb
/dev/sdi: LABEL="CRS1" TYPE="oracleasm" >>>>>>>>>>>>>>>>>>>>>>>>>>/dev/sdi
/dev/mapper/crs1p1: LABEL="CRS1" TYPE="oracleasm"
Disk "CRS2" is a valid ASM disk
/dev/sdc: LABEL="CRS2" TYPE="oracleasm"
/dev/sdj: LABEL="CRS2" TYPE="oracleasm"
/dev/mapper/crs2p1: LABEL="CRS2" TYPE="oracleasm"
Disk "CRS3" is a valid ASM disk
/dev/sdd: LABEL="CRS3" TYPE="oracleasm"
/dev/sdk: LABEL="CRS3" TYPE="oracleasm"
/dev/mapper/crs3p1: LABEL="CRS3" TYPE="oracleasm"
Disk "DATA1" is a valid ASM disk
/dev/sde: LABEL="DATA1" TYPE="oracleasm"
/dev/sdl: LABEL="DATA1" TYPE="oracleasm"
/dev/mapper/data1p1: LABEL="DATA1" TYPE="oracleasm"
Disk "DATA2" is a valid ASM disk
/dev/sdf: LABEL="DATA2" TYPE="oracleasm"
/dev/sdm: LABEL="DATA2" TYPE="oracleasm"
/dev/mapper/data2p1: LABEL="DATA2" TYPE="oracleasm"
Disk "FRA1" is a valid ASM disk
/dev/sdg: LABEL="FRA1" TYPE="oracleasm"
/dev/sdn: LABEL="FRA1" TYPE="oracleasm"
/dev/mapper/fra1p1: LABEL="FRA1" TYPE="oracleasm"

 

 

 

 

 

Changes

 Installing 11.2.0.4 CRS

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.