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


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


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 Oracle Database

Installing Oracle Database


  1. Open Xstart, log in as user oracle, and run the /opt/racinstall/database/runInstaller command to access the GUI of Oracle Universal Installer (OUI).
  2. Enter the /usr/bin/xterm -ls -display $DISPLAY command in the command window, and click Run.


    Use the actual directory where the database installation file is located.

    Figure 4-24 Xstart login dialog box
    Figure 4-25 Accessing the GUI of OUI

  3. Determine whether to receive security updates based on actual needs. In this example, do not select the check box. Click Next and then click Yes in the displayed dialog box.

    Figure 4-26 Configure Security Updates

  4. Select Skip software updates and click Next.

    Figure 4-27 Configure Security Updates

  5. Select Install database software only and click Next.

    Figure 4-28 Select Installation Option

  6. Select Oracle Real Application Clusters database installation and select all nodes.

    Figure 4-29 Grid Installation Options

  7. Click SSH Connectivity, enter the password of user oracle, and click Setup to configure mutual trust.

    Figure 4-30 Grid Installation Options

  8. After the setting is complete, click OK. Click Test to check whether the SSH connection is configured 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 – oracle
    [oracle@dbn01 ~]$ ssh dbn01 date
    The authenticity of host 'dbn01 (' 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,' (ECDSA) to the list of known hosts.
    Thu Dec  7 13:25:09 CST 2017
    [oracle@dbn01 ~]$ ssh dbn02 date
    The authenticity of host 'dbn02 (' 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,' (ECDSA) to the list of known hosts.
    Thu Dec  7 13:25:14 CST 2017 

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

    Figure 4-31 Grid Installation Options

  10. Select and add languages as required. In this example, the default language English is used. Click Next.

    Figure 4-32 Select Product Languages

  11. Select Enterprise Edition and click Next.

    Figure 4-33 Select Database Edition

  12. Specify Oracle software installation paths. Set Oracle Base and Software Location to the directories that have been configured. For details, see Configuring Environment Variables. Click Next.

    Figure 4-34 Specify Installation Location

  13. Specify Oracle user groups by retaining the default values, and click Next.

    Figure 4-35 Privileged Operating System Groups

  14. Perform prerequisite checks. If alarms are displayed, handle them as follows:

    • Task resolv.conf Integrity: Ignore this parsing timeout alarm.
    • Clock Synchronization: Check whether the system NTP clock source is configured successfully. If NTP clock synchronization is normal, ignore this alarm.
    • Single Client Access Name (SCAN): Ignore this alarm. This alarm is displayed if only one SCAN IP address is configured.
      Figure 4-36 Perform Prerequisite Checks

  15. Review the summary and click Install.

    Figure 4-37 Summary

  16. If the database node OS is Red Hat Enterprise Linux 7, the following error message is displayed when the installation progress reaches 56%. Click Continue to continue the installation. After the database software is installed, install patch 19692824 by seeing the official Oracle document (document ID: 1951613.1).

    When installing the patch, perform operations according to the description in the README file in the ZIP package.

  17. 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-38 Install Product

  18. Run the script on each node as user root as instructed, respectively. (The script must be executed on the local node first and then on the remote node.) After the script is successfully executed on all nodes, click Next.

    [root@dbn01 racinstall]# /u01/app/oracle/product/11.2.0/db/ 
     Performing root user operation for Oracle 11g  
     The following environment variables are set as: 
         ORACLE_OWNER= oracle 
         ORACLE_HOME=  /u01/app/oracle/product/11.2.0/db 
    Enter the full pathname of the local bin directory: [/usr/local/bin]:  #Press Enter.
     The contents of "dbhome" have not changed. No need to overwrite. 
     The contents of "oraenv" have not changed. No need to overwrite. 
     The contents of "coraenv" have not changed. No need to overwrite. 
     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. 
     Finished product-specific root actions. 

    Run the script on the dbn02 node.

    [root@dbn02 racinstall]# /u01/app/oracle/product/11.2.0/db/ 
    #Refer to the execution process on the dbn01 node. The command output is omitted here.#

  19. Click Close.

    Figure 4-39 Finish

Updated: 2018-12-26

Document ID: EDOC1100035759

Views: 32522

Downloads: 42

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