LINUXOR.SK ... open source notes ...

Oracle RAC - root.sh output without the patch

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

Oracle RAC Solution · Config document · referenced from Grid patches and the multicast problem

noteThis is a failure, kept for its error message. The fix is in Grid patches and the multicast problem.

The complete output of the first run of root.sh in the Grid home, before patch 17475946 was applied. The script stops with "USM driver install actions failed" before any part of the cluster stack is started. My working notes say the same message came on the second node.

ItemValue
Script/data/u01/app/grid11204/root.sh
Run onoradb01, and with the same result on oradb02
Run asroot
SoftwareGrid Infrastructure 11.2.0.4 as installed from the media, no patch
Operating systemSUSE Linux Enterprise Server 11 SP3
Resultfailed

The command

Run as root on oradb01; the notes list the same command for oradb02.

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

The output

output 45 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]:
   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: /data/u01/app/grid11204/crs/install/crsconfig_params
Creating trace directory
User ignored Prerequisites during installation
Installing Trace File Analyzer
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
Adding Clusterware entries to inittab
USM driver install actions failed
/data/u01/app/grid11204/perl/bin/perl -I/data/u01/app/grid11204/perl/lib -I/data/u01/app/grid11204/crs/install /data/u01/app/grid11204/crs/install/rootcrs.pl execution failed
LineMeaning
Enter the full pathname of the local bin directory: [/usr/local/bin]:The only question the script asks; the default was accepted
Copying dbhome to /usr/local/bin ...First run on this node: the three helper scripts are copied. Later runs report that their contents have not changed
Using configuration parameter file: …/crs/install/crsconfig_paramsThe file that holds the installer's answers for rootcrs.pl
User ignored Prerequisites during installationThe installer was told to continue although prerequisite checks had failed. The line is absent from the two successful outputs
OLR initialization - successful and the wallet linesThe local registry of the node and the certificates of the Grid Plug and Play profile were created
Adding Clusterware entries to inittabThe last step that worked
USM driver install actions failedThe kernel drivers that Grid Infrastructure brings for ACFS could not be installed on this kernel
… rootcrs.pl execution failedroot.sh gives up; no daemon of the cluster stack has been started

The caption of this output in the notes names the missing patch as 1747594; the archive and the directory used to apply it are named 17475946.

Checked against Oracle Grid Infrastructure 26ai

As builtToday
Patch applied after the failed root.shgridSetup.sh -applyRU with -applyOneOffs patches the home during setup, before root.sh runs
ACFS and ADVM drivers on SLES 11 SP3The 11.2 guide lists SLES 11 SP3 as supported for ACFS with 11.2.0.4; the base media nevertheless failed on this kernel. Today the guide lists the supported kernels, for SLES those of 15 SP5 and later
Adding Clusterware entries to inittabSLES 11 uses SysV init. On systemd distributions the stack is started by a unit, and Oracle lists insserv-compat as a required package on SLES 15
← solutionz