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).
Reducing ASM Disk Capacity Online

Reducing ASM Disk Capacity Online

NOTE:
  • Before capacity reduction, confirm with the customer about the number and names of the ASM disks to be deleted, and ensure that all ASM disks to be deleted are dropped from the ASM disk group and rebalance operations are complete.
  • The sequence of mounting the same volume on different database nodes may be different. As a result, the mappings between ASM disk names and device names on different database nodes may be different. Perform the following operations on database nodes separately.
  • In the following operations, the DATADISK020 disk is used as an example.

Procedure

  1. Run the following command on all database nodes to check the device name corresponding to the ASM disk DATADISK020. Record the device name as /dev/sdx for the subsequent volume unmounting and deletion operations.

    [root@dbn01 u01]# ll /dev/asmdisk/ 
    ...
    lrwxrwxrwx 1 root root 6 Jun 29 11:45 DATADISK020 -> ../sdx
    ...

  2. Edit the udev rule file on all database nodes. Delete the rules from the line where the ASM disk DATADISK020 is located, save the file, and exit.

    [root@dbn01 u01]# vi /etc/udev/rules.d/99-oracle-asmdevices.rules  
        

  3. Reload udev rules on all database nodes.

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

    Check whether the udev rules take effect after ASM disk capacity reduction.

     [root@dbn01 u01]# ll /dev/asmdisk/
    

  4. Log in to FusionCube Center, choose Resources > Database > Data Volume Management, click Batch Detach, select /dev/sdx recorded in step 1 on each database node, record the data volume name fc2_DATA_0016 corresponding to the /dev/sdx device on each database node for subsequent volume deletion operations, and click Detach to unmount volumes in batches.

    Batch volume unmounting and deletion operations are risky. Ensure that the device names of data volumes to be deleted are correct. All operations must be performed in a specified period.

  5. After all data volumes to be deleted are unmounted, choose Resources > Database > Data Volume Management, select the check box before the fc2_DATA_0016 list of data volumes to be deleted, and click Delete.
Translation
Download
Updated: 2018-12-26

Document ID: EDOC1100035759

Views: 24993

Downloads: 35

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