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

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

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).
Configuring ASM Disks

Configuring ASM Disks

NOTE:

Use the Linux kernel manager udev to configure the ASM disks. The udev commands may vary on different OSs.

Procedure

  1. Query the SCSI IDs of all shared logical volumes.

    NOTE:

    All volumes are shared volumes. Therefore, you can run the query commands on only one database node.

    • If the database node OS is RHEL 6, run the following commands (the following uses sdb and sdc as an example).
      [root@dbn01~]# /sbin/scsi_id -g -u -d /dev/sdb
      3648fd8e10027e6d80550a12100000027
      [root@dbn01~]# /sbin/scsi_id -g -u -d /dev/sdc
      3648fd8e10027e6d80550a13d00000028
    • If the database node OS is RHEL 7, run the following commands (the following uses sdb and sdc as an example):
      [root@dbn01~]# /usr/lib/udev/scsi_id -g -u -d /dev/sdb
      3648fd8e10027e6d80550a12100000027
      [root@dbn01~]# /usr/lib/udev/scsi_id -g -u -d /dev/sdc
      3648fd8e10027e6d80550a13d00000028

  2. Log in to each database node as user root and edit the udev rule file.

    NOTE:
    • If no file is found, run the vi command to create a file. Each device has a configuration item and each configuration item contains multiple parameters. The SCSI ID of each volume is unique.
    • Configure the following parameters based on the actual situation:
    • RESULT: The format is RESULT=="3688860300000000ae036568967094421". Each device has a unique SCSI ID. You can query the SCSI ID by running the scsi_id -g -u /dev/sdb command.
    • SYMLINK: The format is SYMLINK+="asmdisk/OCRDISK01". asmdisk indicates the folder name of the ASM disk group under /dev/, and OCRDISK01 indicates the ASM disk name. Set this parameter based on the actual situation.
    • OWNER and GROUP: The parameter formats are OWNER="grid" and GROUP="asmadmin". Set the parameters based on the actual situation. The following uses user grid and user group asmadmin as an example.

    Name the volumes in SYMLINK mode. Do not use the NAME mode.

    • If the database node OS is RHEL 6, add the following rules for the disks to be expanded to the rule file (the following uses sdb and sdc as an example):
      [root@dbn01 u01]# vi /etc/udev/rules.d/99-oracle-asmdevices.rules
      KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/$name", RESULT=="3688860300000000ae036568967094421", SYMLINK+="asmdisk/OCRDISK01", OWNER="grid", GROUP="asmadmin", MODE="0660"
      KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/$name", RESULT=="36888603000000009e036568967094421", SYMLINK+="asmdisk/OCRDISK02", OWNER="grid", GROUP="asmadmin", MODE="0660"
      
    • If the database node OS is RHEL 7, add the following rules for the disks to be expanded to the rule file (the following uses sdb and sdc as an example):
      [root@dbn01 u01]# vi /etc/udev/rules.d/99-oracle-asmdevices.rules KERNEL=="sd*", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id --whitelisted --replace-whitespace --device=/dev/$name", RESULT=="3648fd8e1005e339f62e1bfb90000000c", SYMLINK+="asmdisk/OCRDISK01", OWNER="grid", GROUP="asmadmin", MODE="0660"
      KERNEL=="sd*", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id --whitelisted --replace-whitespace --device=/dev/$name", RESULT==" 3648fd8e1005e339f760c521700000004", SYMLINK+="asmdisk/OCRDISK02", OWNER="grid", GROUP="asmadmin", MODE="0660"

  3. Save the file and run the following commands to apply the rules:

    [root@dbn01 u01]# /sbin/udevadm control --reload-rules
    [root@dbn01 u01]# /sbin/udevadm trigger --type=devices --action=change

    Do not run the /sbin/start_udev command to apply the rules when the services are running.

  4. Check whether the ASM disks are configured successfully.

    [root@dbn01 u01]# ll /dev/asmdisk/
    lrwxrwxrwx 1 root root 6 Jul 31 10:40 DATA1 -> ../sdb
    lrwxrwxrwx 1 root root 6 Jul 31 10:40 DATA2 -> ../sdc
    lrwxrwxrwx 1 root root 6 Jul 31 10:40 FRADISK -> ../sdi
    lrwxrwxrwx 1 root root 6 Jul 31 10:01 VDISK1 -> ../sdf
    lrwxrwxrwx 1 root root 6 Jul 31 10:01 VDISK2 -> ../sdg
    lrwxrwxrwx 1 root root 6 Jul 31 10:38 VDISK3 -> ../sdh

Download
Updated: 2019-02-01

Document ID: EDOC1100053123

Views: 14743

Downloads: 14

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