2017-12-02 GI Installation Attempt #3
2017-11-30 De-Install GI
2018-02-01 Revised Planning

Contents

  1. 1 Overview
  2. 2 References
  3. 3 Procedure
    1. 3.1 Installation Attempt #3
    2. 3.2 Verified Installation of CVUQDISK Package
    3. 3.3 Verified avahi-daemon Active
    4. 3.4 Run Root Scripts
    5. 3.5 Check ASM Status

Overview

This is the third attempt at GI installation. I had already uninstalled GI.

References

Procedure

Installation Attempt #3

Followed my procedure in Install GI 12.1.0.2 . However, at Step 16: Prerequisite Checks , I ended up with the following errors:


The details of the errors were:


Verified Installation of CVUQDISK Package

I used the following command to verify the correct version of the cvuqdisk was installed: 

sudo yum list installed cvuqdisk*

The following output confirmed that the package has been installed: 

Loaded plugins: ulninfo
Installed Packages
cvuqdisk.x86_64                        1.0.9-1                         installed

Verified avahi-daemon Active

I used the following command to verify that the avahi-daemon was active: 

sudo systemctl status avahi-daemon

The following output confirmed that the daemon is running: 

• avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2017-12-02 13:46:01 AEDT; 5h 25min ago
 Main PID: 651 (avahi-daemon)
   Status: "avahi-daemon 0.6.31 starting up."
   CGroup: /system.slice/avahi-daemon.service
           ├─651 avahi-daemon: running [redfern1.local]
           └─660 avahi-daemon: chroot helper

Dec 02 13:46:13 redfern1.yaocm.id.au avahi-daemon[651]: New relevant interface eth1.IPv4 for mDNS.
Dec 02 13:46:13 redfern1.yaocm.id.au avahi-daemon[651]: Registering new address record for 192.168.2.140 on eth1.IPv4.
Dec 02 13:46:15 redfern1.yaocm.id.au avahi-daemon[651]: Registering new address record for fe80::216:3eff:fe00:10 on eth2.*.
Dec 02 13:46:17 redfern1.yaocm.id.au avahi-daemon[651]: Joining mDNS multicast group on interface eth2.IPv4 with address 192.168.3.140.
Dec 02 13:46:17 redfern1.yaocm.id.au avahi-daemon[651]: New relevant interface eth2.IPv4 for mDNS.
Dec 02 13:46:17 redfern1.yaocm.id.au avahi-daemon[651]: Registering new address record for 192.168.3.140 on eth2.IPv4.
Dec 02 13:46:20 redfern1.yaocm.id.au avahi-daemon[651]: Registering new address record for fe80::216:3eff:fe00:11 on eth3.*.
Dec 02 13:46:22 redfern1.yaocm.id.au avahi-daemon[651]: Joining mDNS multicast group on interface eth3.IPv4 with address 192.168.4.140.
Dec 02 13:46:22 redfern1.yaocm.id.au avahi-daemon[651]: New relevant interface eth3.IPv4 for mDNS.
Dec 02 13:46:22 redfern1.yaocm.id.au avahi-daemon[651]: Registering new address record for 192.168.4.140 on eth3.IPv4.

However, the message returned by the installer is misleading. When I get the details, I see instead:


I fixed this by running the following command: 

sudo systemctl stop avahi-daemon

The output was: 

Warning: Stopping avahi-daemon.service, but it can still be activated by:
  avahi-daemon.socket

I ignored the remaining prerequisites, and continued the installation.

Run Root Scripts

After the root scripts failed again in Step 18: Install Product , I decided to run the root script manually as follows: 

sudo /opt/app/grid_infra/12.1.0/grid/root.sh

The output was: 

Performing root user operation.

The following environment variables are set as:
    ORACLE_OWNER= oracle
    ORACLE_HOME=  /opt/app/grid_infra/12.1.0/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]: 
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.

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: /opt/app/grid_infra/12.1.0/grid/crs/install/crsconfig_params
2017/12/02 20:51:34 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.

2017/12/02 20:51:59 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.

2017/12/02 20:52:01 CLSRSC-363: User ignored prerequisites during installation

OLR initialization - successful
  root wallet
  root wallet cert
  root cert export
  peer wallet
  profile reader wallet
  pa wallet
  peer wallet keys
  pa wallet keys
  peer cert request
  pa cert request
  peer cert
  pa cert
  peer root cert TP
  profile reader root cert TP
  pa root cert TP
  peer pa cert TP
  pa peer cert TP
  profile reader pa cert TP
  profile reader peer cert TP
  peer user cert
  pa user cert
2017/12/02 20:52:49 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.service'

CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-2672: Attempting to start 'ora.evmd' on 'redfern1'
CRS-2672: Attempting to start 'ora.mdnsd' on 'redfern1'
CRS-2676: Start of 'ora.evmd' on 'redfern1' succeeded
CRS-2676: Start of 'ora.mdnsd' on 'redfern1' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'redfern1'
CRS-2676: Start of 'ora.gpnpd' on 'redfern1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'redfern1'
CRS-2672: Attempting to start 'ora.gipcd' on 'redfern1'
CRS-2676: Start of 'ora.cssdmonitor' on 'redfern1' succeeded
CRS-2676: Start of 'ora.gipcd' on 'redfern1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'redfern1'
CRS-2672: Attempting to start 'ora.diskmon' on 'redfern1'
CRS-2676: Start of 'ora.diskmon' on 'redfern1' succeeded
CRS-2676: Start of 'ora.cssd' on 'redfern1' succeeded

ASM created and started successfully.

Disk Group VOTE created successfully.

2017/12/02 20:58:13 CLSRSC-12: The ASM resource ora.asm did not start

2017/12/02 20:58:14 CLSRSC-258: Failed to configure and start ASM

Died at /opt/app/grid_infra/12.1.0/grid/crs/install/crsinstall.pm line 2017.
The command '/opt/app/grid_infra/12.1.0/grid/perl/bin/perl -I/opt/app/grid_infra/12.1.0/grid/perl/lib -I/opt/app/grid_infra/12.1.0/grid/crs/install /opt/app/grid_infra/12.1.0/grid/crs/install/rootcrs.pl ' execution failed

This is not very helpful.

Check ASM Status

Since the output of the root script said that ASM was started successfully, I checked the status of ASM by using the following command: 

/opt/app/grid_infra/12.1.0/grid/bin/srvctl status asm

The output was: 

PRCR-1070 : Failed to check if resource ora.asm is registered
CRS-0184 : Cannot communicate with the CRS daemon.

At this stage, I am unable to continue. I do not know what the underlying error is.