Oracle RAC - root.sh output on the second node

category: solutionz · date: 2016-12-31 · updated: 2026-10-02 · author: LALA

Oracle RAC Solution · Config document · referenced from Grid Infrastructure installation

The complete output of root.sh in the Grid home on the second node. The node does not create anything shared: it finds the cluster that the first node formed and joins it.

Item	Value
Script	`/data/u01/app/grid11204/root.sh`
Run on	`oradb02`
Run as	root, after `/data/u01/app/oraInventory/orainstRoot.sh` and after `root.sh` had finished on `oradb01`
Software	Grid Infrastructure 11.2.0.4 with patch 17475946
Result	succeeded

The command

Run as root on oradb02.

bash

$ /data/u01/app/grid11204/root.sh

The output

output 24 lines

Performing root user operation for Oracle 11g

The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /data/u01/app/grid11204

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.

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: /data/u01/app/grid11204/crs/install/crsconfig_params
Creating trace directory
Installing Trace File Analyzer
OLR initialization - successful
Adding Clusterware entries to inittab
CRS-4402: The CSS daemon was started in exclusive mode but found an active CSS daemon on node oradb01, number 1, and is terminating
An active cluster was found during exclusive startup, restarting to join the cluster
Configure Oracle Grid Infrastructure for a Cluster ... succeeded

Line	Meaning
`OLR initialization - successful`	The node gets its own local registry. No wallet lines follow: the wallets were made on the first node
`Adding Clusterware entries to inittab`	As on the first node
`CRS-4402: The CSS daemon was started in exclusive mode but found an active CSS daemon on node oradb01, number 1, and is terminating`	The node tried to start alone, found `oradb01` and stopped its exclusive start
`An active cluster was found during exclusive startup, restarting to join the cluster`	The stack restarts as a member of the existing cluster
`Configure Oracle Grid Infrastructure for a Cluster ... succeeded`	The node is in

This is the output of the run that worked. While the interconnect was on a Hyper-V network that passed neither multicast nor broadcast, root.sh on this node failed and the node did not join; the notes kept no output of that failure. See Grid patches and the multicast problem.

The caption of this output in the notes reads "on the first Oracle node (ORADB02)". The command line under it and the content (on node oradb01, number 1) show that it is the second node.