1 Reply Latest reply: Jun 16, 2013 11:04 PM by martin.morono RSS

    Shared resources check for node addition failed Cannot identify existing nodes in cluster The required component "olsnodes" is missing

    martin.morono

      Hi All,

             I have a two-node RAC running on 11.2.0.2 version over Redhat 2.6.18-348.6.1.el5.

       

      Node names are:

      • argalephdblbwl1
      • argalephdblbwl2 (not re-installed yet)

       

      There was some kind of issue with the #2 and we decided to deinstall and reinstall that node again since it's a lab environment.

       

      After deconfiguring and deinstalling the node with no issues, we cannot run the "pre nodeadd" verifications. We get the following error:

       

      {code}

      +ASM1@argalephdblbwl1:/u01/app/oragrid/11.2.0.2/bin>cluvfy stage -pre nodeadd -n argalephdblbwl2 -verbose

       

       

      Performing pre-checks for node addition

      Shared resources check for node addition failed Cannot identify existing nodes in cluster The required component "olsnodes" is missing

       

       

      Verification cannot proceed

      {code}

       

      There is no issues at node #1.

       

       

      {code}

      +ASM1@argalephdblbwl1:/u01/app/oragrid/11.2.0.2/bin>crs_stat

      NAME=ora.DATA1.dg

      TYPE=ora.diskgroup.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.FLASH.dg

      TYPE=ora.diskgroup.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.LISTENER.lsnr

      TYPE=ora.listener.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.LISTENER_SCAN1.lsnr

      TYPE=ora.scan_listener.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.LISTENER_SCAN2.lsnr

      TYPE=ora.scan_listener.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.LISTENER_SCAN3.lsnr

      TYPE=ora.scan_listener.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.QUORUM.dg

      TYPE=ora.diskgroup.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.alephwl.db

      TYPE=ora.database.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.argalephdblbwl1.ASM1.asm

      TYPE=application

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.argalephdblbwl1.LISTENER_ARGALEPHDBLBWL1.lsnr

      TYPE=application

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.argalephdblbwl1.gsd

      TYPE=application

      TARGET=OFFLINE

      STATE=OFFLINE

       

       

      NAME=ora.argalephdblbwl1.ons

      TYPE=application

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.argalephdblbwl1.vip

      TYPE=ora.cluster_vip_net1.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.asm

      TYPE=ora.asm.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.cvu

      TYPE=ora.cvu.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.gsd

      TYPE=ora.gsd.type

      TARGET=OFFLINE

      STATE=OFFLINE

       

       

      NAME=ora.net1.network

      TYPE=ora.network.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.oc4j

      TYPE=ora.oc4j.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.ons

      TYPE=ora.ons.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.registry.acfs

      TYPE=ora.registry.acfs.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.scan1.vip

      TYPE=ora.scan_vip.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.scan2.vip

      TYPE=ora.scan_vip.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1

       

       

      NAME=ora.scan3.vip

      TYPE=ora.scan_vip.type

      TARGET=ONLINE

      STATE=ONLINE on argalephdblbwl1


      {code}

       

      Any suggestion?

       

      Thanks in advance.

       

      Martin

        • 1. Re: Shared resources check for node addition failed Cannot identify existing nodes in cluster The required component "olsnodes" is missing
          martin.morono

          Just FYI, there is no issues with the SSH certificates between nodes:

           

           

          +ASM1@argalephdblbwl1:/u01/app/oragrid/11.2.0.2/bin>/u01/app/oragrid/11.2.0.2/oui/bin/runSSHSetup.sh -user oracle -hosts 'argalephdblbwl1 argalephdblbwl2'  -advanced -exverify

          This script will setup SSH Equivalence from the host 'argalephdblbwl1.turner.com' to specified remote hosts.

           

           

          ORACLE_HOME = /u01/app/oragrid/11.2.0.2

          JAR_LOC = /u01/app/oragrid/11.2.0.2/oui/jlib

          SSH_LOC = /u01/app/oragrid/11.2.0.2/oui/jlib

          OUI_LOC = /u01/app/oragrid/11.2.0.2/oui

          PROP_LOC = /u01/app/oragrid/11.2.0.2/sysman/prov/resources

          JAVA_HOME = /u01/app/oragrid/11.2.0.2/jdk

           

           

          Checking if the remote hosts are reachable.

          formulateLocalCmd argalephdblbwl1/bin/ping-c 1 -w 5

          formulateLocalCmd argalephdblbwl2/bin/ping-c 1 -w 5

          /bin/ping#argalephdblbwl1#-c#1#-w#5

          /bin/ping#argalephdblbwl2#-c#1#-w#5

          Remote host reachability check succeeded.

          All hosts are reachable. Proceeding further...

           

           

           

           

          NOTE :

          As part of the setup procedure, this script will use ssh and scp to copy

          files between the local host and the remote hosts. You may be prompted for

          the password during the execution of the script.

          AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME DIRECTORY

          AND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEDGES TO THESE

          directories.

           

           

          Do you want to continue and let the script make the above mentioned changes (yes/no)?

          yes

           

           

          If The files containing the client public and private keys already exist on the local host. The current private key may or may not have a passphrase associated with it. In case you remember the passphrase and do not want to re-run ssh-keygen, type 'no'. If you type 'yes', the script will remove the old private/public key files and, any previous SSH user setups would be reset.

          Enter 'yes', 'no'

          yes

           

           

          Enter the password: <PASSWORD TYPED>

          Logfile Location : /u01/app/oragrid/11.2.0.2/bin/SSHSetup2013-06-17_12-42-45-AM

          Doing SSHSetup...

          Please be patient, this operation might take sometime...Dont press Ctrl+C...

          Validating remote binaries..

          Remote binaries check succeeded

           

           

          Local Platform:- Linux

           

           

          ------------------------------------------------------------------------

          Verifying SSH setup

          ===================

          The script will now run the date command on the remote nodes using ssh

          to verify if ssh is setup correctly. IF THE SETUP IS CORRECTLY SETUP,

          THERE SHOULD BE NO OUTPUT OTHER THAN THE DATE AND SSH SHOULD NOT ASK FOR

          PASSWORDS. If you see any output other than date or are prompted for the

          password, ssh is not setup correctly and you will need to resolve the

          issue and set up ssh again.

          The possible causes for failure could be:

          1. The server settings in /etc/ssh/sshd_config file do not allow ssh

          for user oracle.

          2. The server may have disabled public key based authentication.

          3. The client public key on the server may be outdated.

          4. ~oracle or ~oracle/.ssh on the remote host may not be owned by oracle.

          5. User may not have passed -shared option for shared remote users or

          may be passing the -shared option for non-shared remote users.

          6. If there is output in addition to the date, but no password is asked,

          it may be a security alert shown as part of company policy. Append the

          additional text to the <OMS HOME>/sysman/prov/resources/ignoreMessages.txt file.

          ------------------------------------------------------------------------

          --argalephdblbwl1:--

          Running /usr/bin/ssh -x -l oracle argalephdblbwl1 date to verify SSH connectivity has been setup from local host to argalephdblbwl1.

          IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.

          Mon Jun 17 00:43:28 GMT+3 2013

          ------------------------------------------------------------------------

          --argalephdblbwl2:--

          Running /usr/bin/ssh -x -l oracle argalephdblbwl2 date to verify SSH connectivity has been setup from local host to argalephdblbwl2.

          IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.

          Mon Jun 17 00:43:53 GMT+3 2013

          ------------------------------------------------------------------------

          ------------------------------------------------------------------------

          Verifying SSH connectivity has been setup from argalephdblbwl1 to argalephdblbwl1

          ------------------------------------------------------------------------

          IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.

          Mon Jun 17 00:43:29 GMT+3 2013

          ------------------------------------------------------------------------

          ------------------------------------------------------------------------

          Verifying SSH connectivity has been setup from argalephdblbwl1 to argalephdblbwl2

          ------------------------------------------------------------------------

          IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.

          Mon Jun 17 00:43:53 GMT+3 2013

          ------------------------------------------------------------------------

          -Verification from argalephdblbwl1 complete-

          ------------------------------------------------------------------------

          Verifying SSH connectivity has been setup from argalephdblbwl2 to argalephdblbwl1

          ------------------------------------------------------------------------

          IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.

          Mon Jun 17 00:43:29 GMT+3 2013

          ------------------------------------------------------------------------

          ------------------------------------------------------------------------

          Verifying SSH connectivity has been setup from argalephdblbwl2 to argalephdblbwl2

          ------------------------------------------------------------------------

          IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.

          Mon Jun 17 00:43:54 GMT+3 2013

          ------------------------------------------------------------------------

          -Verification from argalephdblbwl2 complete-

          SSH verification complete.