KunLun Mission Critical Server Oracle Database Oracle 12c R1 (RAC) Best Practice 02

Procedure

1. Log in to dbn01 as user grid and select a proper graphical display scheme.
2. Navigate to the directory of the Grid Infrastructure installation package and run the following commands to perform a check:

   [grid@dbn01 ~]$ cd /opt/racinstall/grid/
   [grid@dbn01 grid]$ ./runcluvfy.sh stage -pre crsinst -n dbn01,dbn02 -verbose

   NOTE:

   Ignore the following error:

   1. The "/dev/shm mounted as temporary file system" alarm is generated due to a bug of Oracle. The cluvfy check does not check whether /dev/shm is mounted but checks the configuration information of /dev/shm in /etc/fstab. You can ignore this alarm.

      Starting check for /dev/shm mounted as temporary file system ...
      ERROR:
      PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm
      PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm
      PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm
      PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm
      Check for /dev/shm mounted as temporary file system failed

   2. If other errors occur, rectify the error by referring to the error messages.

3. Navigate to the directory of the Grid Infrastructure installation package and run the runInstaller script.

   [grid@dbn01 ~]$ cd /opt/racinstall/grid/
   [grid@dbn01 grid]$ ./runInstaller

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

5. Select Configure a Standard cluster and click Next.

6. Select Advanced Installation and click Next.

7. Select languages and click Next (English is selected by default).

8. Change the value of SCAN Name. Ensure that the value is consistent with the SCAN name corresponding to the SCAN IP address in the /hosts file. SCAN Port is 1521 by default. Deselect Configure GNS, and click Next.

9. Click Add to add information about another node. Ensure that the information is consistent with the information in the /etc/hosts file. Then click OK.

10. Select SSH Connectivity, enter the password of user grid, and click Setup to establish the SSH trust relationship between the two nodes. Then click OK.

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

    On RHEL, the system may display the following error information. You need to enter yes on each node during the first interaction between the nodes. Log in to each database node, manually establish the SSH connection, enter yes. And then click Test again.

12. When the following dialog box is displayed, click OK. Then click Next.

13. Confirm the network port information, and set Interface Type corresponding to the VIP network port to Public. Set Interface Type corresponding to the priv network port to Private. If other management IP addresses exist, set Interface Type to Do not use. And then click Next.

14. Select Use Standard ASM for storage and click Next.

15. Configure the OCR disk group. Set Redundancy to Normal and retain the default value 1 (MB) for Allocation Unit Size. Click Change Discovery Path. In the displayed dialog box, enter the absolute path of the ASM disk /dev/asmdisk/*, and click OK. Then select the vdisk disks in the list, and click Next.

16. Select Use same passwords for these accounts, configure a password for users SYS and ASMSNMP, and click Next.

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

18. Retain the default settings (the check box is not selected), and click Next.

19. Retain the default ASM user groups, and click Next.

20. Specify the installation paths of Oracle Grid Infrastructure. Set Oracle base and Software location to the directories that have been configured during environment variable configuration, and click Next.

21. Retain the default value of Inventory Directory and click Next.

22. Deselect Automatically run configuration scripts and click Next.

23. The system may display alarms during the check. The recommended handling methods are as follows:
    • "OS Kernel Parameter: panic_on_oops": This alarm is generated due to bug 18468128 of Oracle. To clear the alarm, add kernel.panic_on_oops = 1 to the /etc/sysctl.conf file, and run the sysctl –p command to apply the modification.
    • "Task resolv.conf Integrity": This is a parsing timeout alarm and you can ignore it.
    • "DNS/NIS name service": This alarm is reported if the DNS server is not used during SCAN IP address configuration. You can ignore this alarm.
    • "/dev/shm mounted as temporary file system": This alarm is generated due to a bug of Oracle. The cluvfy check does not check whether /dev/shm is mounted but checks the configuration information of /dev/shm in /etc/fstab. You can ignore this alarm.
    • If the system reports other alarms, contact the database administrator for confirmation before performing the installation.

24. Select Ignore All to ignore the alarms and click Next. In the displayed dialog box, click Yes.

25. Check the installation summary and click Install.

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

    Run the su - or su – root command to switch to user root. Run the orainstRoot.sh script on the dbn01 node first. After the script is executed on the dbn01 node, run the orainstRoot.sh script on the dbn02 node. Then run the root.sh script on the dbn01 node. After the script is executed on the dbn01 node, run the root.sh script on the dbn02 node.

    The command output of the orainstRoot.sh script is as follows.

    During the execution of the root.sh script, you need to press Enter manually.

    The command output of the root.sh script is as follows.

27. After the preceding scripts are executed, click OK to continue the installation. Ignore the "Oracle Cluster Verification Utility failed" message displayed when the progress reaches 100%, click OK, and click Next. In the displayed dialog box, click Yes.

28. Click Close. Oracle Grid Infrastructure is installed on both nodes.