Shut Down, Reset, or Power Cycle the Oracle MiniCluster S7-2 Engineered System

Hi,

In this post, I want to share the required steps for Startup, Shut Down, Reset, or Power Cycle the Oracle MiniCluster S7-2 Engineered System.

Notify affected users that the server will be shut down.
Log into one of the nodes as an MCMU administrator such as mcinstall

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu status -G -k

List a Summary of All DB VM Groups

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu tenant -G -l

Stop the DB grid infrastructure

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -G -n VMgroupname

Here, where VMgroupname is the name of the DB VM group. You can learn with “mcmu tenant -G -l”

Stop the GI in the kernel zones on node1 and node2.

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -G -k node1
mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -G -k node2

Re-check Workgroup status

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu status -G -k

Shut down all the zones in VM group dpwyadm

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -V -n dpwyadm

Check running status

mcinstall@dpwadm-n1:/var/home/mcinstall % zoneadm list -civ

If there are “running” state then stop the kernel zones.

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -Z -k node1
[INFO ] Log file path : dpwadm-n1:/var/opt/oracle.minicluster/setup/logs/mcmu_121818_131505.log
[INFO ] Check if initial setup complete
[INFO ] Checking if nodes are in sync
Do you want to shut down zone acfskz? [yes/no] (no): yes
[INFO ] Zone acfskz has been shut down
mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -Z -k node2
[INFO ] Log file path : dpwadm-n1:/var/opt/oracle.minicluster/setup/logs/mcmu_121818_131716.log
[INFO ] Check if initial setup complete
[INFO ] Checking if nodes are in sync
Do you want to shut down zone acfskz? [yes/no] (no): yes
[INFO ] Zone acfskz has been shut down

OR You want to shut down the whole system with one command.

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -S

Shutdown one node:

mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -N node1
mcinstall@dpwadm-n1:/var/home/mcinstall % mcmu stop -N node2

For a full power down, perform the remaining steps. Now, you can stop ILOMs. Oracle ILOM CLI – In a terminal window, enter:

Oracle(R) Integrated Lights Out Manager

Version 4.0.2.2.c r124557

Copyright (c) 2018, Oracle and/or its affiliates. All rights reserved.

Warning: HTTPS certificate is set to factory default.

Hostname: dpwadm-n1-ilom

-> stop /System/
Are you sure you want to stop /System (y/n)? y
Stopping /System

For Starting the whole system, Log in to ILOMs

Oracle(R) Integrated Lights Out Manager

Version 4.0.2.2.c r124557

Copyright (c) 2018, Oracle and/or its affiliates. All rights reserved.

Warning: HTTPS certificate is set to factory default.

Hostname: dpwadm-n1-ilom

-> start /System

Check System

-> show /System/

/System
Targets:
Open_Problems (0)
Processors
Memory
Power
Cooling
Storage
Networking
PCI_Devices
Firmware
Log

Properties:
health = OK
health_details = –
open_problems_count = 0
type = Rack Mount
model = MiniCluster S7-2
qpart_id = XXXXXXXX
part_number = MiniCluster S7-2
serial_number = XXXXXXXXXX
component_model = SPARC S7-2
component_part_number = XXXXXXX
component_serial_number = XXXXXXXX
system_identifier = Oracle MiniCluster S7-2 XXXXXXXXXX
system_fw_version = Sun System Firmware 9.8.5.c 2018/05/03 17:22
primary_operating_system = Oracle Solaris 11.3 SPARC
primary_operating_system_detail = –
host_primary_mac_address = 00:10:e0:c0:bf:30
ilom_address = 10.102.106.141
ilom_mac_address = 00:10:E0:C0:BF:39
locator_indicator = Off
power_state = Off
actual_power_consumption = 471 watts
action = (Cannot show property)

Commands:
cd
reset
set
show
start
stop

->

Also please check for faults.

Oracle(R) Integrated Lights Out Manager

Version 4.0.2.2.c r124557

Copyright (c) 2018, Oracle and/or its affiliates. All rights reserved.

Warning: HTTPS certificate is set to factory default.

Hostname: dpwadm-n1-ilom

-> start /SP/faultmgmt/shell/
Are you sure you want to start /SP/faultmgmt/shell (y/n)? y

faultmgmtsp>
faultmgmtsp> fmadm faulty
No faults found
faultmgmtsp> exit

Now, log into one of the nodes as an MCMU administrator such as mcinstall and check the system

zoneadm list -civ

mcmu status -G -k

Advertisements

How To Rename A Pluggable Database- PDB

Hi,

I need to rename a pluggable database. It is so easy to rename.7

Let’s do it step by step:

1. Firstly set containter to PDB named DEV

alter session set container=DEV;
2. shutdown and open it in restricted mode.
shutdown immediate;
startup open restrict;
3. Now rename the PDB
alter pluggable database DEV rename global_name to ACC;
4. Check it
show con_name;
show pdbs;
5. shutdown and start in normal mode.
shutdown immediate;
startup;
6. Verify
select name,open_mode from v$pdbs;

Changing the Character Set for a RAC Database Fails with an ORA-12720

Hi,

Changing the Character set for a RAC Database fails with below ORA-12720 error.

ORA-02374: conversion error loading table “RTLSDPROD”.”ZIF_CRANE_MSG_LOG”
ORA-12899: value too large for column MCHN_ID (actual: 11, maximum: 10)
ORA-02372: data for row: MCHN_ID : 0X’52880000603400006034′

The CLUSTER_DATABASE parameter must be temporarily changed in order  to alter the database character set. This will require a shutdown of the entire database (all instances).

Let’s do it step by step

Step 1: Shutdown all instances.

Step 2: On Node1, edit the initialization parameter CLUSTER_DATABASE and set it to FALSE

CLUSTER_DATABASE = FALSE

Step 3: Startup mount the instance in exclusive mode:

SQLPLUS> startup mount exclusive

Step 4: Issue the following commands:

alter system enable restricted session;
alter system set job_queue_processes = 0;
alter system set aq_tm_processes = 0;
alter database open;

Step 5: Change the character set.

Step 6: Shutdown the instance to enable parallel server.

SQLPLUS> shutdown immediate

Step 7: On Node1, edit the init.ora parameter CLUSTER_DATABASE  and set it to TRUE.

CLUSTER_DATABASE = TRUE

Step 8: Start up all the instances accessing the database.

Changing the Oracle Database Characterset.

Hello,

If you want to change your database character set due to do some requirements.

Let’s do it step by step

1. Check your current database settings

SQL> set line999
SQL> select * from v$nls_parameters;
PARAMETER                VALUE
--------------           --------------
NLS_LANGUAGE             AMERICAN
NLS_TERRITORY           AMERICA
NLS_CURRENCY            $
NLS_ISO_CURRENCY        AMERICA
NLS_NUMERIC_CHARACTERS  .,
NLS_CALENDAR            GREGORIAN
NLS_DATE_FORMAT         DD-MON-RR
NLS_DATE_LANGUAGE       AMERICAN
NLS_CHARACTERSET        UTF8
NLS_SORT                BINARY
NLS_TIME_FORMAT         HH.MI.SSXFF AM

PARAMETER               VALUE
--------------          --------------
NLS_TIMESTAMP_FORMAT    DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT      HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY       $
NLS_NCHAR_CHARACTERSET  AL16UTF16
NLS_COMP                BINARY
NLS_LENGTH_SEMANTICS    BYTE
NLS_NCHAR_CONV_EXCP     FALSE

2. Shutdown Database

SQL> SHUTDOWN IMMEDIATE;
Database closed.
Database dismounted.
ORACLE instance shut down.

3. Follow the below steps:

SQL> STARTUP MOUNT;
SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0; 
SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
SQL> ALTER DATABASE OPEN;
SQL> ALTER DATABASE CHARACTER SET internal_use WE8ISO8859P9;
SQL> SHUTDOWN IMMEDIATE; 
SQL> startup;

It is OK!

Oracle Database 18c Grid Infrastructure Installation On Oracle Linux 7.5

Hi,

Let’s install Oracle Database 18c Grid Infrastructure on Oracle Linux 7.5 step by step

1- Download the setup file from below link:

https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

2- Add your IP addresses to your “/etc/hosts” on all nodes . Also register your IP addresses into your DNS server.

#public ip

192.168.5.11  veridata1

192.168.5.12 veridata2

#vip ip

192.168.5.121 veridata1-vip

192.168.5.122 veridata2-vip

#private ip

10.32.50.21  veridata1-priv

10.32.50.22  veridata2-priv

#scan ip

192.168.5.123 orcscan

192.168.5.124 orcscan

192.168.5.125 orcscan

3-Change the selinux to disabled

vi /etc/selinux/config

SELINUX=disabled

4-If you have the Linux firewall enabled, you will need to disable it.

systemctl stop firewalld

systemctl disable firewalld

5-On each node within the Oracle RAC Database cluster, stop and disable the avahi services run the following commands:

 # systemctl stop avahi-dnsconfd

# systemctl stop avahi-daemon

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

avahi-daemon.socket

To keep the avahi services off persistently across reboots, on each node run the following:

# systemctl disable avahi-dnsconfd

# systemctl disable avahi-daemon

rm ‘/etc/systemd/system/dbus-org.freedesktop.Avahi.service’

rm ‘/etc/systemd/system/multi-user.target.wants/avahi-daemon.service’

rm ‘/etc/systemd/system/sockets.target.wants/avahi-daemon.socket’

6-Set the following kernel parameters on both nodes.

vi /etc/sysctl.conf

fs.file-max = 6815744

kernel.sem = 250 32000 100 128

kernel.shmmni = 4096

kernel.shmall = 1073741824

kernel.shmmax = 4398046511104

kernel.panic_on_oops = 1

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 1048576

net.ipv4.conf.all.rp_filter = 2

net.ipv4.conf.default.rp_filter = 2

fs.aio-max-nr = 1048576

net.ipv4.ip_local_port_range = 9000 65500

6- Run the following command to apply the current kernel parameters.

/sbin/sysctl -p

7-Set the following lines to below file

vi /etc/security/limits.d/oracle-database-preinstall-18c.conf

oracle   soft   nofile    1024

oracle   hard   nofile    65536

oracle   soft   nproc    16384

oracle   hard   nproc    16384

oracle   soft   stack    10240

oracle   hard   stack    32768

oracle   hard   memlock    134217728

oracle   soft   memlock    134217728

8-The following packages are required, including the 32-bit version of some of the packages.

yum install -y bc

yum install -y binutils

yum install -y compat-libcap1

yum install -y compat-libstdc++-33

yum install -y compat-libstdc++-33.i686

yum install -y elfutils-libelf.i686

yum install -y elfutils-libelf

yum install -y elfutils-libelf-devel.i686

yum install -y elfutils-libelf-devel

yum install -y fontconfig-devel

yum install -y glibc.i686

yum install -y glibc

yum install -y glibc-devel.i686

yum install -y glibc-devel

yum install -y ksh

yum install -y libaio.i686

yum install -y libaio

yum install -y libaio-devel.i686

yum install -y libaio-devel

yum install -y libX11.i686

yum install -y libX11

yum install -y libXau.i686

yum install -y libXau

yum install -y libXi.i686

yum install -y libXi

yum install -y libXtst.i686

yum install -y libXtst

yum install -y libgcc.i686

yum install -y libgcc

yum install -y librdmacm-devel

yum install -y libstdc++.i686

yum install -y libstdc++

yum install -y libstdc++-devel.i686

yum install -y libstdc++-devel

yum install -y libxcb.i686

yum install -y libxcb

yum install -y make

yum install -y nfs-utils

yum install -y net-tools

yum install -y python

yum install -y python-configshell

yum install -y python-rtslib

yum install -y python-six

yum install -y smartmontools

yum install -y sysstat

yum install -y targetcli

yum install -y unixODBC

yum install -y yum install librdmacm-devel

yum install -y libaio-devel*.x86_64.rpm

yum install -y ksh*.x86_64

9-Create the directories and users on both nodes in which the Oracle software will be installed.

groupadd -g 1000 oinstall

groupadd -g 1001 dba

–Optional

groupadd -g 1002 oper

groupadd -g 1003 backupdba

groupadd -g 1004 dgdba

groupadd -g 1005 kmdba

groupadd -g 1006 asmdba

groupadd -g 1007 asmoper

groupadd -g 1008 asmadmin

groupadd -g 1009 racdbamkdir -p /u01/app/18.0.0.0/grid

mkdir -p /u01/app/oracle

mkdir -p /u01/app/oracle/product/18.0.0.0/db_1

chown -R grid:oinstall /u01

chown -R oracle:oinstall /u01/app/oracle

chmod -R 775 /u01

10- Log in as the oracle and grid user and add the following lines at the end of the “.bash_profile” file.

export ORACLE_SID=+ASM1

export ORACLE_BASE=/u01/app/grid

export ORACLE_HOME=/u01/app/18.0.0.0/grid

export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

alias base=”cd $ORACLE_BASE”

alias oh=”cd $ORACLE_HOME”

Edit oracle user profile

export ORACLE_SID=orcl

export ORACLE_BASE=/u01/app/oracle

export ORACLE_HOME=$ORACLE_BASE/product/18.0.0.0/db_1

export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

alias base=”cd $ORACLE_BASE”

alias oh=”cd $ORACLE_HOME”

11-As grid user login node1 and unzip setup zip file

[grid@node1 tmp]$ unzip LINUX.X64_180000_grid_home.zip -d /u01/app/18.0.0.0/grid/

12- Install the following package from the grid home as the “root” user on all nodes.

[root@node1 grid]# rpm -ivh /u01/app/18.0.0.0/grid/cv/rpm/cvuqdisk-1.0.10-1.rpm

Preparing…                          ################################# [100%]

Using default group oinstall to install package

Updating / installing…

1:cvuqdisk-1.0.10-1                ################################# [100%]

13- Run gridSetup.sh located in grid home directory as the “grid” user.

[grid@node1 grid]$ ./gridSetup.sh

14- It will prompt for executing orainstRoot.sh and root.sh scripts on both nodes as root user.

[root@node1 ~]# /u01/app/oraInventory/orainstRoot.sh

Changing permissions of /u01/app/oraInventory.

Adding read,write permissions for group.

Removing read,write,execute permissions for world.

 

Changing groupname of /u01/app/oraInventory to oinstall.

The execution of the script is complete.

 [root@node1 ~]# /u01/app/18.0.0.0/grid/root.sh

Performing root user operation.

 

The following environment variables are set as:

    ORACLE_OWNER= oracle

    ORACLE_HOME=  /u01/app/18.0.0.0/grid

 

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.

Relinking oracle with rac_on option

Using configuration parameter file: /u01/app/18.0.0.0/grid/crs/install/crsconfig_params

The log of current session can be found at:

  /u01/app/grid/crsdata/node1/crsconfig/rootcrs_node1_2019-03-29_12-18-36AM.log

2019/03/29 12:18:48 CLSRSC-594: Executing installation step 1 of 20: ‘SetupTFA’.

2019/03/29 12:18:48 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.

2019/03/29 12:19:11 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.

2019/03/29 12:19:11 CLSRSC-594: Executing installation step 2 of 20: ‘ValidateEnv’.

2019/03/29 12:19:11 CLSRSC-363: User ignored prerequisites during installation

2019/03/29 12:19:11 CLSRSC-594: Executing installation step 3 of 20: ‘CheckFirstNode’.

2019/03/29 12:19:13 CLSRSC-594: Executing installation step 4 of 20: ‘GenSiteGUIDs’.

2019/03/29 12:19:17 CLSRSC-594: Executing installation step 5 of 20: ‘SaveParamFile’.

2019/03/29 12:19:26 CLSRSC-594: Executing installation step 6 of 20: ‘SetupOSD’.

2019/03/29 12:19:27 CLSRSC-594: Executing installation step 7 of 20: ‘CheckCRSConfig’.

2019/03/29 12:19:27 CLSRSC-594: Executing installation step 8 of 20: ‘SetupLocalGPNP’.

2019/03/29 12:19:47 CLSRSC-594: Executing installation step 9 of 20: ‘CreateRootCert’.

2019/03/29 12:19:54 CLSRSC-594: Executing installation step 10 of 20: ‘ConfigOLR’.

2019/03/29 12:20:08 CLSRSC-594: Executing installation step 11 of 20: ‘ConfigCHMOS’.

2019/03/29 12:20:09 CLSRSC-594: Executing installation step 12 of 20: ‘CreateOHASD’.

2019/03/29 12:20:17 CLSRSC-594: Executing installation step 13 of 20: ‘ConfigOHASD’.

2019/03/29 12:20:17 CLSRSC-330: Adding Clusterware entries to file ‘oracle-ohasd.service’

2019/03/29 12:21:11 CLSRSC-594: Executing installation step 14 of 20: ‘InstallAFD’.

2019/03/29 12:21:20 CLSRSC-594: Executing installation step 15 of 20: ‘InstallACFS’.

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘node1’

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘node1’ has completed

CRS-4133: Oracle High Availability Services has been stopped.

CRS-4123: Oracle High Availability Services has been started.

2019/03/29 12:22:21 CLSRSC-594: Executing installation step 16 of 20: ‘InstallKA’.

2019/03/29 12:22:29 CLSRSC-594: Executing installation step 17 of 20: ‘InitConfig’.

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘node1’

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘node1’ has completed

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 ‘node1’

CRS-2672: Attempting to start ‘ora.mdnsd’ on ‘node1’

CRS-2676: Start of ‘ora.evmd’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.mdnsd’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.gpnpd’ on ‘node1’

CRS-2676: Start of ‘ora.gpnpd’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.cssdmonitor’ on ‘node1’

CRS-2672: Attempting to start ‘ora.gipcd’ on ‘node1’

CRS-2676: Start of ‘ora.cssdmonitor’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.gipcd’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.cssd’ on ‘node1’

CRS-2672: Attempting to start ‘ora.diskmon’ on ‘node1’

CRS-2676: Start of ‘ora.diskmon’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.cssd’ on ‘node1’ succeeded

 

[INFO] [DBT-30001] Disk groups created successfully. Check /u01/app/grid/cfgtoollogs/asmca/asmca-190329PM122306.log for details.

 

 

2019/03/29 12:24:07 CLSRSC-482: Running command: ‘/u01/app/18.0.0.0/grid/bin/ocrconfig -upgrade oracle oinstall’

CRS-2672: Attempting to start ‘ora.crf’ on ‘node1’

CRS-2672: Attempting to start ‘ora.storage’ on ‘node1’

CRS-2676: Start of ‘ora.storage’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.crf’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.crsd’ on ‘node1’

CRS-2676: Start of ‘ora.crsd’ on ‘node1’ succeeded

CRS-4256: Updating the profile

Successful addition of voting disk d287f2540f014f4abf99589bfacba98c.

Successfully replaced voting disk group with +DATA.

CRS-4256: Updating the profile

CRS-4266: Voting file(s) successfully replaced

##  STATE    File Universal Id                File Name Disk group

—  —–    —————–                ——— ———

  1. ONLINE d287f2540f014f4abf99589bfacba98c (/dev/oracleasm/disks/ORADATA1) [DATA]

Located 1 voting disk(s).

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘node1’

CRS-2673: Attempting to stop ‘ora.crsd’ on ‘node1’

CRS-2677: Stop of ‘ora.crsd’ on ‘node1’ succeeded

CRS-2673: Attempting to stop ‘ora.storage’ on ‘node1’

CRS-2673: Attempting to stop ‘ora.crf’ on ‘node1’

CRS-2673: Attempting to stop ‘ora.drivers.acfs’ on ‘node1’

CRS-2673: Attempting to stop ‘ora.mdnsd’ on ‘node1’

CRS-2677: Stop of ‘ora.crf’ on ‘node1’ succeeded

CRS-2677: Stop of ‘ora.storage’ on ‘node1’ succeeded

CRS-2673: Attempting to stop ‘ora.asm’ on ‘node1’

CRS-2677: Stop of ‘ora.drivers.acfs’ on ‘node1’ succeeded

CRS-2677: Stop of ‘ora.mdnsd’ on ‘node1’ succeeded

CRS-2677: Stop of ‘ora.asm’ on ‘node1’ succeeded

CRS-2673: Attempting to stop ‘ora.cluster_interconnect.haip’ on ‘node1’

CRS-2677: Stop of ‘ora.cluster_interconnect.haip’ on ‘node1’ succeeded

CRS-2673: Attempting to stop ‘ora.ctssd’ on ‘node1’

CRS-2673: Attempting to stop ‘ora.evmd’ on ‘node1’

CRS-2677: Stop of ‘ora.ctssd’ on ‘node1’ succeeded

CRS-2677: Stop of ‘ora.evmd’ on ‘node1’ succeeded

CRS-2673: Attempting to stop ‘ora.cssd’ on ‘node1’

CRS-2677: Stop of ‘ora.cssd’ on ‘node1’ succeeded

CRS-2673: Attempting to stop ‘ora.gipcd’ on ‘node1’

CRS-2673: Attempting to stop ‘ora.gpnpd’ on ‘node1’

CRS-2677: Stop of ‘ora.gpnpd’ on ‘node1’ succeeded

CRS-2677: Stop of ‘ora.gipcd’ on ‘node1’ succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘node1’ has completed

CRS-4133: Oracle High Availability Services has been stopped.

2019/03/29 12:26:57 CLSRSC-594: Executing installation step 18 of 20: ‘StartCluster’.

CRS-4123: Starting Oracle High Availability Services-managed resources

CRS-2672: Attempting to start ‘ora.evmd’ on ‘node1’

CRS-2672: Attempting to start ‘ora.mdnsd’ on ‘node1’

CRS-2676: Start of ‘ora.mdnsd’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.evmd’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.gpnpd’ on ‘node1’

CRS-2676: Start of ‘ora.gpnpd’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.gipcd’ on ‘node1’

CRS-2676: Start of ‘ora.gipcd’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.crf’ on ‘node1’

CRS-2672: Attempting to start ‘ora.cssdmonitor’ on ‘node1’

CRS-2676: Start of ‘ora.cssdmonitor’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.cssd’ on ‘node1’

CRS-2672: Attempting to start ‘ora.diskmon’ on ‘node1’

CRS-2676: Start of ‘ora.diskmon’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.crf’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.cssd’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.cluster_interconnect.haip’ on ‘node1’

CRS-2672: Attempting to start ‘ora.ctssd’ on ‘node1’

CRS-2676: Start of ‘ora.ctssd’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.cluster_interconnect.haip’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.asm’ on ‘node1’

CRS-2676: Start of ‘ora.asm’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.storage’ on ‘node1’

CRS-2676: Start of ‘ora.storage’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.crsd’ on ‘node1’

CRS-2676: Start of ‘ora.crsd’ on ‘node1’ succeeded

CRS-6023: Starting Oracle Cluster Ready Services-managed resources

CRS-6017: Processing resource auto-start for servers: node1

CRS-6016: Resource auto-start has completed for server node1

CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources

CRS-4123: Oracle High Availability Services has been started.

2019/03/29 12:28:26 CLSRSC-343: Successfully started Oracle Clusterware stack

2019/03/29 12:28:26 CLSRSC-594: Executing installation step 19 of 20: ‘ConfigNode’.

CRS-2672: Attempting to start ‘ora.ASMNET1LSNR_ASM.lsnr’ on ‘node1’

CRS-2672: Attempting to start ‘ora.ASMNET2LSNR_ASM.lsnr’ on ‘node1’

CRS-2676: Start of ‘ora.ASMNET2LSNR_ASM.lsnr’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.ASMNET1LSNR_ASM.lsnr’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.asm’ on ‘node1’

CRS-2676: Start of ‘ora.asm’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.DATA.dg’ on ‘node1’

CRS-2676: Start of ‘ora.DATA.dg’ on ‘node1’ succeeded

2019/03/29 12:29:53 CLSRSC-594: Executing installation step 20 of 20: ‘PostConfig’.

2019/03/29 12:31:05 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster … succeeded

ON NODE 2

[root@node2 ~]# /u01/app/oraInventory/orainstRoot.sh

Changing permissions of /u01/app/oraInventory.

Adding read,write permissions for group.

Removing read,write,execute permissions for world.

Changing groupname of /u01/app/oraInventory to oinstall.

The execution of the script is complete.

[root@node2 ~]# /u01/app/18.0.0.0/grid/root.sh

Performing root user operation.

 

The following environment variables are set as:

    ORACLE_OWNER= oracle

    ORACLE_HOME=  /u01/app/18.0.0.0/grid

 

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.

Relinking oracle with rac_on option

Using configuration parameter file: /u01/app/18.0.0.0/grid/crs/install/crsconfig_params

The log of current session can be found at:

  /u01/app/grid/crsdata/node2/crsconfig/rootcrs_node2_2019-03-29_12-33-39AM.log

2019/03/29 12:33:41 CLSRSC-594: Executing installation step 1 of 20: ‘SetupTFA’.

2019/03/29 12:33:41 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.

2019/03/29 12:34:05 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.

2019/03/29 12:34:05 CLSRSC-594: Executing installation step 2 of 20: ‘ValidateEnv’.

2019/03/29 12:34:05 CLSRSC-363: User ignored prerequisites during installation

2019/03/29 12:34:05 CLSRSC-594: Executing installation step 3 of 20: ‘CheckFirstNode’.

2019/03/29 12:34:06 CLSRSC-594: Executing installation step 4 of 20: ‘GenSiteGUIDs’.

2019/03/29 12:34:06 CLSRSC-594: Executing installation step 5 of 20: ‘SaveParamFile’.

2019/03/29 12:34:08 CLSRSC-594: Executing installation step 6 of 20: ‘SetupOSD’.

2019/03/29 12:34:08 CLSRSC-594: Executing installation step 7 of 20: ‘CheckCRSConfig’.

2019/03/29 12:34:09 CLSRSC-594: Executing installation step 8 of 20: ‘SetupLocalGPNP’.

2019/03/29 12:34:10 CLSRSC-594: Executing installation step 9 of 20: ‘CreateRootCert’.

2019/03/29 12:34:10 CLSRSC-594: Executing installation step 10 of 20: ‘ConfigOLR’.

2019/03/29 12:34:11 CLSRSC-594: Executing installation step 11 of 20: ‘ConfigCHMOS’.

2019/03/29 12:34:12 CLSRSC-594: Executing installation step 12 of 20: ‘CreateOHASD’.

2019/03/29 12:34:13 CLSRSC-594: Executing installation step 13 of 20: ‘ConfigOHASD’.

2019/03/29 12:34:13 CLSRSC-330: Adding Clusterware entries to file ‘oracle-ohasd.service’

2019/03/29 12:34:57 CLSRSC-594: Executing installation step 14 of 20: ‘InstallAFD’.

2019/03/29 12:34:58 CLSRSC-594: Executing installation step 15 of 20: ‘InstallACFS’.

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘node2’

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘node2’ has completed

CRS-4133: Oracle High Availability Services has been stopped.

CRS-4123: Oracle High Availability Services has been started.

2019/03/29 12:35:49 CLSRSC-594: Executing installation step 16 of 20: ‘InstallKA’.

2019/03/29 12:35:50 CLSRSC-594: Executing installation step 17 of 20: ‘InitConfig’.

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘node2’

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘node2’ has completed

CRS-4133: Oracle High Availability Services has been stopped.

CRS-4123: Oracle High Availability Services has been started.

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘node2’

CRS-2673: Attempting to stop ‘ora.drivers.acfs’ on ‘node2’

CRS-2677: Stop of ‘ora.drivers.acfs’ on ‘node2’ succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘node2’ has completed

CRS-4133: Oracle High Availability Services has been stopped.

2019/03/29 12:35:59 CLSRSC-594: Executing installation step 18 of 20: ‘StartCluster’.

CRS-4123: Starting Oracle High Availability Services-managed resources

CRS-2672: Attempting to start ‘ora.evmd’ on ‘node2’

CRS-2672: Attempting to start ‘ora.mdnsd’ on ‘node2’

CRS-2676: Start of ‘ora.mdnsd’ on ‘node2’ succeeded

CRS-2676: Start of ‘ora.evmd’ 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.gipcd’ on ‘node2’

CRS-2676: Start of ‘ora.gipcd’ on ‘node2’ succeeded

CRS-2672: Attempting to start ‘ora.crf’ on ‘node2’

CRS-2672: Attempting to start ‘ora.cssdmonitor’ on ‘node2’

CRS-2676: Start of ‘ora.cssdmonitor’ 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.crf’ on ‘node2’ succeeded

CRS-2676: Start of ‘ora.cssd’ on ‘node2’ succeeded

CRS-2672: Attempting to start ‘ora.cluster_interconnect.haip’ on ‘node2’

CRS-2672: Attempting to start ‘ora.ctssd’ on ‘node2’

CRS-2676: Start of ‘ora.ctssd’ on ‘node2’ succeeded

CRS-2676: Start of ‘ora.cluster_interconnect.haip’ on ‘node2’ succeeded

CRS-2672: Attempting to start ‘ora.asm’ on ‘node2’

CRS-2676: Start of ‘ora.asm’ on ‘node2’ succeeded

CRS-2672: Attempting to start ‘ora.storage’ on ‘node2’

CRS-2676: Start of ‘ora.storage’ on ‘node2’ succeeded

CRS-2672: Attempting to start ‘ora.crsd’ on ‘node2’

CRS-2676: Start of ‘ora.crsd’ on ‘node2’ succeeded

CRS-6017: Processing resource auto-start for servers: node2

CRS-2673: Attempting to stop ‘ora.LISTENER_SCAN1.lsnr’ on ‘node1’

CRS-2672: Attempting to start ‘ora.ASMNET1LSNR_ASM.lsnr’ on ‘node2’

CRS-2672: Attempting to start ‘ora.ASMNET2LSNR_ASM.lsnr’ on ‘node2’

CRS-2672: Attempting to start ‘ora.ons’ on ‘node2’

CRS-2677: Stop of ‘ora.LISTENER_SCAN1.lsnr’ on ‘node1’ succeeded

CRS-2673: Attempting to stop ‘ora.scan1.vip’ on ‘node1’

CRS-2677: Stop of ‘ora.scan1.vip’ on ‘node1’ succeeded

CRS-2672: Attempting to start ‘ora.scan1.vip’ on ‘node2’

CRS-2676: Start of ‘ora.ASMNET1LSNR_ASM.lsnr’ on ‘node2’ succeeded

CRS-2676: Start of ‘ora.ASMNET2LSNR_ASM.lsnr’ on ‘node2’ succeeded

CRS-2672: Attempting to start ‘ora.asm’ on ‘node2’

CRS-2676: Start of ‘ora.scan1.vip’ on ‘node2’ succeeded

CRS-2672: Attempting to start ‘ora.LISTENER_SCAN1.lsnr’ on ‘node2’

CRS-2676: Start of ‘ora.LISTENER_SCAN1.lsnr’ on ‘node2’ succeeded

CRS-2676: Start of ‘ora.ons’ on ‘node2’ succeeded

CRS-2676: Start of ‘ora.asm’ on ‘node2’ succeeded

CRS-2672: Attempting to start ‘ora.proxy_advm’ on ‘node1’

CRS-2672: Attempting to start ‘ora.proxy_advm’ on ‘node2’

CRS-2676: Start of ‘ora.proxy_advm’ on ‘node1’ succeeded

CRS-2676: Start of ‘ora.proxy_advm’ on ‘node2’ succeeded

CRS-6016: Resource auto-start has completed for server node2

CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources

CRS-4123: Oracle High Availability Services has been started.

2019/03/29 12:38:59 CLSRSC-343: Successfully started Oracle Clusterware stack

2019/03/29 12:38:59 CLSRSC-594: Executing installation step 19 of 20: ‘ConfigNode’.

2019/03/29 12:39:09 CLSRSC-594: Executing installation step 20 of 20: ‘PostConfig’.

2019/03/29 12:39:14 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster … succeeded

 

After executing scripts click OK and you can Close installation screen.

Now, your 18c RAC is ready.