5 Replies Latest reply: Dec 11, 2012 7:28 PM by Victor Armbrust RSS

    root.sh failed to execute

    979251
      sh root.sh
      Running Oracle 11g root.sh script...

      The following environment variables are set as:
      ORACLE_OWNER= oracle
      ORACLE_HOME= /u01/app/11.2.0/grid

      Enter the full pathname of the local bin directory: [usr/local/bin]: /usr/local/bin
      The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)
      [n]: y
      Copying dbhome to /usr/local/bin ...
      The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
      [n]: y
      Copying oraenv to /usr/local/bin ...
      The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
      [n]: y
      Copying coraenv to /usr/local/bin ...

      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.sh script.
      Now product-specific root actions will be performed.
      2012-12-11 17:31:03: Parsing the host name
      2012-12-11 17:31:03: Checking for super user privileges
      2012-12-11 17:31:03: User has super user privileges
      Using configuration parameter file: /u01/app/11.2.0/grid/crs/install/crsconfig_params
      Improper Oracle Clusterware configuration found on this host
      Deconfigure the existing cluster configuration before starting
      to configure a new Clusterware
      run '/u01/app/11.2.0/grid/crs/install/rootcrs.pl -deconfig'
      to configure existing failed configuration and then rerun root.sh
      abc-Prod-DB:/u01/app/11.2.0/grid # /u01/app/11.2.0/grid/crs/install/rootcrs.pl -deconfig
      2012-12-11 17:31:12: Parsing the host name
      2012-12-11 17:31:12: Checking for super user privileges
      2012-12-11 17:31:12: User has super user privileges
      Using configuration parameter file: /u01/app/11.2.0/grid/crs/install/crsconfig_params
      Oracle Clusterware stack is not active on this node
      Restart the clusterware stack (use /u01/app/11.2.0/grid/bin/crsctl start crs) and retry
      Failed to verify resources
      abc-Prod-DB:/u01/app/11.2.0/grid # /u01/app/11.2.0/grid/bin/crsctl start crs
      Failure at scls_scr_setval with code 8
      Internal Error Information:
      Category: -2
      Operation: failed
      Location: scrsearch3
      Other: id doesnt exist scls_scr_setval
      System Dependent Information: 2

      CRS-4000: Command Start failed, or completed with errors.
        • 1. Re: root.sh failed to execute
          Victor Armbrust
          Have you already installed/configure a Grid installation? Have you attended to all pre-reqs before the Grid installation? Which install documentation are you using?
          Which OS?
          • 2. Re: root.sh failed to execute
            979251
            Yes i already did all the pre reqs i dont know exactly may be i am missing something

            here is the link which i followed

            http://www.oracle-base.com/articles/11g/oracle-db-11gr2-rac-installation-on-ol5-using-vmware-server-2.php

            my os is Suse linux 11 enterprise edition
            • 3. Re: root.sh failed to execute
              Victor Armbrust
              The doc is fine. I suggest you to cleanup any failed installation and try again

              Victor
              • 4. Re: root.sh failed to execute
                979251
                Thanks for the reply victor

                can you please suggest any steps to cleanup or deconfig for reinitiating the configuration.

                sorry for this as i am new in doing clustering this the first time i am installing cluster
                • 5. Re: root.sh failed to execute
                  Victor Armbrust
                  Hi

                  The best way is to use the MOS NOTE ID: How to Proceed from Failed 11gR2 Grid Infrastructure (CRS) Installation [ID 942166.1]     

                  ------


                  GI Cluster Deconfigure and Reconfigure

                  Identify cause of root.sh failure by reviewing logs in $GRID_HOME/cfgtoollogs/crsconfig and $GRID_HOME/log, once cause is identified and problem is fixed, deconfigure and reconfigure with steps below - keep in mind that you will need wait till each step finishes successfully before move to next one:

                  Step 0: For 11.2.0.2 and above, root.sh is restartable.

                  Once cause is identified and the problem is fixed, root.sh can be executed again on the failed node. If it succeeds, continue with your planned installation procedure; otherwise as root sequentially execute "$GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force" and $GRID_HOME/root.sh on local node, if it succeeds, continue with your planned installation procedure, otherwise proceed to next step (Step 1) of the note.

                  Step 1: As root, run "$GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force" on all nodes, except the last one.

                  Step 2: As root, run "$GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force -lastnode" on last node. This command will zero out OCR, Voting Disk and the ASM diskgroup for OCR and Voting Disk

                  Note:

                  a. Step1 and 2 can be skipped on node(s) where root.sh haven't been executed this time.

                  b. Step1 and 2 should remove checkpoint file. To verify:

                  ls -l $ORACLE_BASE/Clusterware/ckptGridHA_.xml

                  If it's still there, please remove it manually with "rm" command on all nodes

                  c. If GPNP profile is different between nodes/setup, clean it up on all nodes as grid user

                  $ rm -rf $GRID_HOME/gpnp/*
                  $ mkdir -p $GRID_HOME/gpnp/profiles/peer $GRID_HOME/gpnp/wallets/peer $GRID_HOME/gpnp/wallets/prdr $GRID_HOME/gpnp/wallets/pa $GRID_HOME/gpnp/wallets/root

                  The profile needs to be cleaned up:

                  c1. If root.sh is executed concurrently - one should not execute root.sh on any other nodes before it finishes on first node.

                  c2. If network info, location of OCR or Voting Disk etc changed after Grid is installed - rare


                  Step 3: As root, run $GRID_HOME/root.sh on first node

                  Step 4: As root, run $GRID_HOME/root.sh on all other node(s), except last one.

                  Step 5: As root, run $GRID_HOME/root.sh on last node.

                  ------

                  Victor