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).
Installing Grid Infrastructure

Installing Grid Infrastructure

NOTE:

Perform the following operations on all database nodes.

Procedure

  1. Start Xstart, and log in as user grid.
  2. In the command window, enter the /opt/racinstall/grid/runInstaller command, and click Run.

    The installation starts.
    Figure 4-1 Xstart login dialog box
    Figure 4-2 Grid Infrastructure installation directory

  3. In the Grid Infrastructure installation wizard window, select Skip software updates and click Next.

    Figure 4-3 Download Software Updates

  4. Select Install and Configure Oracle Grid Infrastructure for a Cluster and click Next.

    Figure 4-4 Select Installation Option

  5. Select Advanced Installation and click Next.

    Figure 4-5 Select Installation Type

  6. Select the language to be used, add it to the Selected Languages box, and click Next.

    Figure 4-6 Select Product Languages

  7. Deselect Configure GNS, and change the value of SCAN Name. Ensure that the value is the same as the SCAN name corresponding to the SCAN IP address in /etc/hosts. Click Next.

    Figure 4-7 Grid Plug and Play Information

  8. Click Add to add information of another node, and click OK.

    Add information of all nodes in sequence.
    Figure 4-8 Cluster Node Information

  9. Establish the SSH equivalency relationship between the nodes.

    Select SSH Connectivity, enter the password of user grid, and click Setup.
    Figure 4-9 Cluster Node Information

  10. Click Test to verify that the SSH trust relationship is established successfully.

    In some Red Hat Enterprise Linux scenarios, the following error information is displayed. The cause is that you need to enter yes during the first interaction between nodes. Log in to all database nodes, manually execute the SSH connection, enter yes, and click Test again. (The dbn01 node in the following information is used as an example.)
    [root@dbn01 ~]# su – grid
    
    [grid@dbn01 ~]$ ssh dbn01 date
    The authenticity of host 'dbn01 (192.168.100.111)' can't be established.
    ECDSA key fingerprint is b0:4a:db:ee:16:68:4a:56:9e:67:c5:0b:d7:63:4a:c6.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'dbn01,192.168.100.111' (ECDSA) to the list of known hosts.
    Thu Dec  7 13:25:09 CST 2017
    
    [grid@dbn01 ~]$ ssh dbn02 date
    The authenticity of host 'dbn02 (192.168.100.112)' can't be established.
    ECDSA key fingerprint is 52:b6:72:1c:ff:69:f8:fd:3a:dc:24:7a:03:34:88:7b.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'dbn02,192.168.100.112' (ECDSA) to the list of known hosts.
    Thu Dec  7 13:25:14 CST 2017 

  11. After the following dialog box is displayed, click OK. Then click Next.

  12. Check whether the network interface attributes are correct based on the network segment attributes in etc/hosts. Then click Next.

    Figure 4-10 Specify Network Interface Usage

  13. Select Oracle Automatic Storage Management (Oracle ASM). Then click Next.

    Figure 4-11 Storage Option Information

  14. Set related parameters to create an ASM disk group, and click Next.

    • Disk Group Name: Enter an ASM disk group name. (Example: OCR)
    • Redundancy: Select Normal.
    • AU Size: Retain the default value 1.
    • Select All Disks. If the disk list is empty, click Change Discovery Path to change the disk discovery path to /dev/asmdisk/*, and select OCRDISK01, OCRDISK02, and OCRDISK03, OCRDISK04, and OCRDISK05 in the disk list.

      Select disks based on the actual ASM labels created.

      Figure 4-12 Create ASM Disk Group

  15. Select Use same passwords for these accounts, set the same password for users SYS and ASMSNMP, and click Next.

    Figure 4-13 Specify ASM Password

  16. Select Do not use Intelligent Platform Management Interface (IPMI), and click Next.

    Figure 4-14 Failure Isolation Support

  17. Specify ASM user groups by retaining the default values, and click Next.

    Figure 4-15 Privileged Operating System Groups

  18. Specify Grid software installation paths. Set Oracle Base and Software Location to the directories that have been configured. For details, see the configuration information in Configuring Environment Variables. The value of Software Location cannot be a subdirectory of the value of Oracle Base. After the paths are specified, click Next.

    Figure 4-16 Specify Installation Location

  19. Set Inventory Directory to the default value, and click Next.

    Figure 4-17 Create Inventory

  20. Check for alarms. You are advised to handle the alarms as follows:

    • Ignore the Device Checks for ASM alarm.
    • Ignore the Task resolv.conf Integrity parsing timeout alarm.
    • The Package pdksh-5.2.14 alarm is displayed only when the database node OS is Red Hat Enterprise Linux 6. ksh and mksh are installed by default. You do not need to install pdksh and you can ignore this alarm. If pdksh is required, install it. For details, see Installing RPM Packages.
    • Click Fix & Check Again for the OS Kernel Parameters alarm. Log in to all displayed database nodes as user root, run the runfixup.sh script, configure parameters, and click OK.
    Figure 4-18 Perform Prerequisite Checks

  21. In the Summary window, click Install.

    Figure 4-19 Summary

  22. When the following dialog box is displayed, run the scripts on the two database nodes as user root in sequence to complete the installation.

    Figure 4-20 Install Product

  23. Switch to user root and run the /u01/app/oraInventory/orainstRoot.sh script. After the execution on the local node is complete, run the script on the other node.

    NOTE:
    • Run the su - or su - root command to switch to user root and ensure complete environment settings. Do not run the sudo, pbrun, su root, or su command.
    [root@dbn01 racinstall]# /u01/app/oraInventory/orainstRoot.sh 
    Changing permissions of /u01/app/oraInventory. 
    Adding read,write permissions for group. 
    Removing read,write,execute permissions for world. 
    Changing groupname of /u01/app/oraInventory to oinstall. 
    The execution of the script is complete.     

    Run the script on the dbn02 node.

    [root@dbn02 racinstall]# /u01/app/oraInventory/orainstRoot.sh 
    #For details, see the execution process on the dbn01 node. The command output is not presented here.#
    • If the database node OS is Red Hat Enterprise Linux 7, install the Grid patch 18370031 according to the official Oracle document (document ID: 1951613.1) before running the root.sh script. After the installation is successful, run the /u01/app/11.2.0/grid/root.sh script.
      NOTE:
      • When installing the patch, perform operations according to the description in the README file in the ZIP package.
      • In the current scenario, perform operations based on the Case 5 scenario in section 2.3 "Patch Installation" in the README file.
    • If the database node OS is Oracle Linux 6 or Red Hat Enterprise Linux 6, run the /u01/app/11.2.0/grid/root.sh script after the /u01/app/oraInventory/orainstRoot.sh script is executed on all database nodes.
      NOTE:

      Run the /u01/app/11.2.0/grid/root.sh script on another node after it is successfully executed on the local node. Run the script on all nodes in the sequence of environment variable SIDs of user oracle.

    [root@dbn01~]# /u01/app/11.2.0/grid/root.sh  
    Performing root user operation for Oracle 11g  
    The following environment variables are set as: 
        ORACLE_OWNER= grid 
        ORACLE_HOME= /u01/app/11.2.0/grid 
    Enter the full pathname of the local bin directory: [/usr/local/bin]:  #Press Enter.
       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: /u01/app/11.2.0/grid/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 upstart 
    CRS-2672: Attempting to start 'ora.mdnsd' on 'dbn01' 
    CRS-2676: Start of 'ora.mdnsd' on 'dbn01' succeeded 
    CRS-2672: Attempting to start 'ora.gpnpd' on 'dbn01' 
    CRS-2676: Start of 'ora.gpnpd' on 'dbn01' succeeded 
    CRS-2672: Attempting to start 'ora.cssdmonitor' on 'dbn01' 
    CRS-2672: Attempting to start 'ora.gipcd' on 'dbn01' 
    CRS-2676: Start of 'ora.cssdmonitor' on 'dbn01' succeeded 
    CRS-2676: Start of 'ora.gipcd' on 'dbn01' succeeded 
    CRS-2672: Attempting to start 'ora.cssd' on 'dbn01' 
    CRS-2672: Attempting to start 'ora.diskmon' on 'dbn01' 
    CRS-2676: Start of 'ora.diskmon' on 'dbn01' succeeded 
    CRS-2676: Start of 'ora.cssd' on 'dbn01' succeeded 
    ASM created and started successfully. 
    Disk Group OCR created successfully. 
    clscfg: -install mode specified 
    Successfully accumulated necessary OCR keys. 
    Creating OCR keys for user 'root', privgrp 'root'.. 
    Operation successful. 
    CRS-4256: Updating the profile 
    Successful addition of voting disk 1265aa2a11a74fe6bf15911462aff6e1. 
    Successful addition of voting disk 5d28aa696f794f1fbf1ed78107ca91d1. 
    Successful addition of voting disk 207beb7ab88f4f77bf5d7b64cc1d033c. 
    Successfully replaced voting disk group with +OCR. 
    CRS-4256: Updating the profile 
    CRS-4266: Voting file(s) successfully replaced 
    ##  STATE    File Universal Id                File Name Disk group 
    --  -----    -----------------                --------- --------- 
     1. ONLINE   1265aa2a11a74fe6bf15911462aff6e1 (/dev/asmdisk/OCRDISK01) [OCR] 
     2. ONLINE   5d28aa696f794f1fbf1ed78107ca91d1 (/dev/asmdisk/OCRDISK02) [OCR] 
     3. ONLINE   207beb7ab88f4f77bf5d7b64cc1d033c (/dev/asmdisk/OCRDISK03) [OCR] 
    Located 3 voting disk(s). 
    CRS-2672: Attempting to start 'ora.asm' on 'dbn01' 
    CRS-2676: Start of 'ora.asm' on 'dbn01' succeeded 
    CRS-2672: Attempting to start 'ora.OCR.dg' on 'dbn01' 
    CRS-2676: Start of 'ora.OCR.dg' on 'dbn01' succeeded 
    Configure Oracle Grid Infrastructure for a Cluster ... succeeded     

    Run the script on the dbn02 node.

    [root@dbn02~]# /u01/app/11.2.0/grid/root.sh  
    #For details, see the execution process on the dbn01 node. The command output is not presented here.#

  24. After the execution is complete, click OK. Ignore the "[INS-20802] Oracle Cluster Verification Utility failed" message that is displayed when the progress reaches 100%.

    Figure 4-21 Install Product

  25. Click Yes, and click Next.

    Figure 4-22 Install Product

  26. Click Close.

    Figure 4-23 Finish

Translation
Download
Updated: 2018-12-26

Document ID: EDOC1100035759

Views: 20364

Downloads: 30

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