No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionCube DB 3.1 Database Best Practice 03 (Oracle RAC 11g R2)

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Automatic Trust Relationship Configuration Failure

Automatic Trust Relationship Configuration Failure

If error information is displayed after step 8 in Installing Grid Infrastructure and step 6 in 5.4.1 are performed, manually configure the trust relationship. This section uses user oracle as an example. Perform the following operations:

  1. Create keys for nodes.

    [root@dbn01 ~]# su - oracle 
    [oracle@dbn01 ~]# mkdir ~/.ssh 
    [oracle@dbn01 ~]# chmod 700 ~/.ssh 
    [oracle@dbn01 ~]# ssh-keygen -t rsa 
    [oracle@dbn01 ~]# ssh-keygen -t dsa 
    [root@dbn02 ~]# su - oracle 
    [oracle@dbn02 ~]# mkdir ~/.ssh 
    [oracle@dbn02 ~]# chmod 700 ~/.ssh 
    [oracle@dbn02 ~]# ssh-keygen -t rsa 
    [oracle@dbn02 ~]# ssh-keygen -t dsa     

  2. Perform trust relationship configuration on the dbn01 node.

    [oracle@dbn01 ~]# touch ~/.ssh/authorized_keys 
    [oracle@dbn01 ~]# cd ~/.ssh 
    [oracle@dbn01 .ssh]# ssh dbn01 cat ~/.ssh/id_rsa.pub >> authorized_keys 
    [oracle@dbn01 .ssh]# ssh dbn02 cat ~/.ssh/id_rsa.pub >> authorized_keys 
    [oracle@dbn01 .ssh]# ssh dbn01 cat ~/.ssh/id_dsa.pub >> authorized_keys 
    [oracle@dbn01 .ssh]# ssh dbn02 cat ~/.ssh/id_dsa.pub >> authorized_keys     

  3. Send the verification file containing public key information from the dbn01 node to the dbn02 node.

    [oracle@dbn01 .ssh]# scp authorized_keys dbn02: /home/oracle/.ssh 
    oracle@dbn02's password: 
    authorized_keys 100% 1644 1.6KB/s 00:00     

  4. Set the verification file permission on all nodes.

    [oracle@dbn01 .ssh]# chmod 600 ~/.ssh/authorized_keys 
    [oracle@dbn02 .ssh]# chmod 600 ~/.ssh/authorized_keys     

  5. Enable user consistency. Run the following commands on the node running OUI (dbn01 as an example) as user oracle:

    [oracle@dbn01 .ssh]# exec /usr/bin/ssh-agent $SHELL 
    [oracle@dbn01 .ssh]# ssh-add 
    Identity added: /home/oracle/.ssh/id_rsa (/home/oracle/.ssh/id_rsa) 
    Identity added: /home/oracle/.ssh/id_dsa (/home/oracle/.ssh/id_dsa)     

  6. Check whether the SSH configuration is correct. Run the following commands as user oracle on both nodes:

    NOTE:
    • Run the following commands on each node.
    • When running each command for the first time, enter yes to confirm the command.
    • If you do not run these commands, the following information will be displayed during Clusterware installation even if the SSH configuration is complete:

      The specified nodes are not clusterable

      ssh dbn01 date 
      ssh dbn02 date 
      ssh dbn01-priv date 
      ssh dbn02-priv date 

Translation
Download
Updated: 2018-12-26

Document ID: EDOC1100035759

Views: 24132

Downloads: 32

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next