Using configuration parameter file: /opt/app/19.x.0/grid/crs/install/crsconfig_params The log of current session can be found at: /opt/app/oracle/crsdata/rhel71/crsconfig/rootcrs_rhel71_2019-06-03_05-55-22AM.log 2019/06/03 05:55:34 CLSRSC-594: Executing installation step 1 of 19: 'SetupTFA'. 2019/06/03 05:55:34 CLSRSC-594: Executing installation step 2 of 19: 'ValidateEnv'. 2019/06/03 05:55:34 CLSRSC-363: User ignored prerequisites during installation 2019/06/03 05:55:34 CLSRSC-594: Executing installation step 3 of 19: 'CheckFirstNode'. 2019/06/03 05:55:34 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector. 2019/06/03 05:55:38 CLSRSC-594: Executing installation step 4 of 19: 'GenSiteGUIDs'. 2019/06/03 05:55:39 CLSRSC-594: Executing installation step 5 of 19: 'SetupOSD'. 2019/06/03 05:55:39 CLSRSC-594: Executing installation step 6 of 19: 'CheckCRSConfig'. 2019/06/03 05:55:40 CLSRSC-594: Executing installation step 7 of 19: 'SetupLocalGPNP'. 2019/06/03 05:55:42 CLSRSC-594: Executing installation step 8 of 19: 'CreateRootCert'. 2019/06/03 05:55:48 CLSRSC-594: Executing installation step 9 of 19: 'ConfigOLR'. 2019/06/03 05:55:49 CLSRSC-594: Executing installation step 10 of 19: 'ConfigCHMOS'. 2019/06/03 05:56:22 CLSRSC-594: Executing installation step 11 of 19: 'CreateOHASD'. 2019/06/03 05:56:24 CLSRSC-594: Executing installation step 12 of 19: 'ConfigOHASD'. 2019/06/03 05:56:24 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.service' 2019/06/03 05:56:47 CLSRSC-594: Executing installation step 13 of 19: 'InstallAFD'. 2019/06/03 05:56:49 CLSRSC-594: Executing installation step 14 of 19: 'InstallACFS'. 2019/06/03 05:56:52 CLSRSC-594: Executing installation step 15 of 19: 'InstallKA'. 2019/06/03 05:56:57 CLSRSC-594: Executing installation step 16 of 19: 'InitConfig'. CRS-2672: Attempting to start 'ora.evmd' on 'rhel71' CRS-2672: Attempting to start 'ora.mdnsd' on 'rhel71' CRS-2676: Start of 'ora.mdnsd' on 'rhel71' succeeded CRS-2676: Start of 'ora.evmd' on 'rhel71' succeeded CRS-2672: Attempting to start 'ora.gpnpd' on 'rhel71' CRS-2676: Start of 'ora.gpnpd' on 'rhel71' succeeded CRS-2672: Attempting to start 'ora.cssdmonitor' on 'rhel71' CRS-2672: Attempting to start 'ora.gipcd' on 'rhel71' CRS-2676: Start of 'ora.cssdmonitor' on 'rhel71' succeeded CRS-2674: Start of 'ora.gipcd' on 'rhel71' failed CRS-2673: Attempting to stop 'ora.cssdmonitor' on 'rhel71' CRS-2677: Stop of 'ora.cssdmonitor' on 'rhel71' succeeded CRS-2673: Attempting to stop 'ora.gpnpd' on 'rhel71' CRS-2677: Stop of 'ora.gpnpd' on 'rhel71' succeeded CRS-2673: Attempting to stop 'ora.mdnsd' on 'rhel71' CRS-2677: Stop of 'ora.mdnsd' on 'rhel71' succeeded CRS-2673: Attempting to stop 'ora.evmd' on 'rhel71' CRS-2677: Stop of 'ora.evmd' on 'rhel71' succeeded CRS-4000: Command Start failed, or completed with errors. 2019/06/03 05:58:40 CLSRSC-119: Start of the exclusive mode cluster failed Died at /opt/app/19.x.0/grid/crs/install/crsinstall.pm line 2439.There are multiple MOS notes on root.sh failures as there are many different reasons for root.sh failures. But in this case MOS nor any of the logs generated during the installation revealed the real reason, hence this post.
Reason for this failure was the length of the cluster name. It seems the cluster name, which should be between 1 - 15 characters in length is never checked during the response file parsing (field oracle.install.crs.config.clusterName) or when installing via OUI to see if it is over the 15 character limit. Therefore it's possible to begin an installation with a cluster name longer than 15 characters as shown below (where the cluster name is 17 char long).
However, as shown earlier the installation will fail at root.sh execution time. Therefore, if root.sh fails on the first node check the length of the cluster name conform to the limit set by Oracle.
Related Post
Changing The Cluster Name
