Solution to the Problem of changing the mutipath link when installing Oracle11gR2Linux

Source: Internet
Author: User
Install three nodes for a set of oracle11gr2, but the dm paths of the multipath disks found by the three nodes are inconsistent, and the corresponding dm paths change after the restart:

Install three nodes on a set of oracle 11gr2, but the dm paths of the multipath disks found by the three nodes are inconsistent, and the corresponding dm paths change after the restart:

Install three nodes on a set of Oracle 11gr2, but the dm paths of the multipath disks found by the three nodes are inconsistent, and the corresponding dm paths change after the restart:

[Root @ db3 ~] # Multipath-l | grep dm
Mpath2 (3600140000125d8a5200003000008a0000) dm-1 HP, HSV 400
|-3: 0: 1: 1 sdm 8: 192 active undef running
Mpath1 (3600140000125d8a5200003000008e0000) dm-0 HP, HSV 400
Mpath9 (3600140000125d8a520000300000aa0000) dm-8 HP, HSV 400
Mpath8 (360014213125d8a520000300000a20000) dm-6 HP, HSV 400
Mpath7 (3600140000125d8a520000300000a60000) dm-7 HP, HSV 400
Mpath6 (3600140000125d8a5200003000009a0000) dm-4 HP, HSV 400
Mpath5 (3600140000125d8a5200003000009e0000) dm-3 HP, HSV 400
Mpath11 (360014213125d8a520000300000b20000) dm-10 HP, HSV 400
Mpath4 (3600140000125d8a520000300000960000) dm-5 HP, HSV 400
Mpath10 (3600140000125d8a520000300000ae0000) dm-9 HP, HSV 400
Mpath3 (3600140000125d8a520000300000920000) dm-2 HP, HSV 400

[Root @ db1 ~] # Multipath-l | grep dm
Mpath2 (3600140000125d8a520000300000920000) dm-2 HP, HSV 400
Mpath1 (3600140000125d8a5200003000008e0000) dm-0 HP, HSV 400
Mpath9 (3600140000125d8a520000300000ae0000) dm-9 HP, HSV 400
Mpath8 (3600140000125d8a520000300000aa0000) dm-8 HP, HSV 400
Mpath7 (3600140000125d8a520000300000a60000) dm-6 HP, HSV 400
Mpath6 (3600140000125d8a520000300000a20000) dm-7 HP, HSV 400
Mpath5 (3600140000125d8a5200003000009e0000) dm-4 HP, HSV 400
Mpath11 (3600140000125d8a5200003000008a0000) dm-1 HP, HSV 400
|-3: 0: 1: 1 sdm 8: 192 active undef running
Mpath4 (3600140000125d8a5200003000009a0000) dm-5 HP, HSV 400
Mpath10 (360014213125d8a520000300000b20000) dm-10 HP, HSV 400
Mpath3 (3600140000125d8a520000300000960000) dm-3 HP, HSV 400

[Root @ db2 oraInventory] # multipath-l | grep dm
Mpath2 (3600140000125d8a520000300000920000) dm-2 HP, HSV 400
Mpath1 (3600140000125d8a5200003000008e0000) dm-1 HP, HSV 400
Mpath9 (3600140000125d8a520000300000ae0000) dm-9 HP, HSV 400
Mpath8 (3600140000125d8a520000300000aa0000) dm-8 HP, HSV 400
Mpath7 (3600140000125d8a520000300000a60000) dm-7 HP, HSV 400
Mpath6 (3600140000125d8a520000300000a20000) dm-6 HP, HSV 400
Mpath5 (3600140000125d8a5200003000009e0000) dm-5 HP, HSV 400
Mpath11 (3600140000125d8a5200003000008a0000) dm-0 HP, HSV 400
|-3: 0: 1: 1 sdm 8: 192 active undef running
Mpath4 (3600140000125d8a5200003000009a0000) dm-4 HP, HSV 400
Mpath10 (360014213125d8a520000300000b20000) dm-10 HP, HSV 400
Mpath3 (3600140000125d8a520000300000960000) dm-3 HP, HSV 400

By changing/etc/multipath/bindings and/etc/multipath. in the conf file, the mpath paths of the three machines are consistent, but the dm paths are inconsistent. You can only use the/dev/mapper/multipath disk as the ASM shared disk.

Fdisk/dev/mapper/multipath * is used for partitioning. When installing grid infrastructure and creating an asm volume group, run/dev/mapper/multipath to report "not an available asm disk ", because oracleasm, asmlib, and asm-support are not installed at this time, the problem cannot be determined. Because the installed version is Red Hat linux 6.2, the oracle official website does not support the asmlib package. You can only reinstall the operating system and reduce the operating system version to linux 5.7.

After installing the operating system and configuring the three oracleasm packages, run the oracleasm command to add a multipath Disk:

Oracleasm createdisk DISK1/dev/mapper/mpath * p1

The other two machines are loaded, loaded successfully, and the added drive letter can be found. However, the major and minor numbers of the three machines created in the/dev/oracleasm/disks/directory of the asm disk are inconsistent. In this case, you can only try to install the grid. When the asm volume group is created, the asm DISK is successfully added. However, when the installation environment is checked, the following error occurs:

Device Checks for ASM-This is a pre-check to verify if the specified devices meet the requirements for configuration through the Oracle Universal Storage Manager Configuration Assistant. Error:
-
"/Dev/oracleasm/disks/DISK1" is not shared-Cause: Cause Of Problem Not Available-Action: User Action Not Available
-
"/Dev/oracleasm/disks/DISK2" is not shared-Cause: Cause Of Problem Not Available-Action: User Action Not Available
-
"/Dev/oracleasm/disks/DISK3" is not shared-Cause: Cause Of Problem Not Available-Action: User Action Not Available
-
Cocould not find the storage-Cause: Cause Of Problem Not Available-Action: User Action Not Available
-
Cocould not find the storage-Cause: Cause Of Problem Not Available-Action: User Action Not Available

Operation Failed on Nodes: [db3, db2, db1]
Verification result of failed node: db3

Details:
-
PRVF-5150: Path/dev/oracleasm/disks/DISK5 is not a valid path on all nodes-Cause:-Action:
-
PRVF-5150: Path/dev/oracleasm/disks/DISK4 is not a valid path on all nodes-Cause:-Action:
-
PRVF-5149: WARNING: Storage "/dev/oracleasm/disks/DISK3" is not shared on all nodes-Cause:-Action:
-
PRVF-5149: WARNING: Storage "/dev/oracleasm/disks/DISK2" is not shared on all nodes-Cause:-Action:
-
PRVF-5149: WARNING: Storage "/dev/oracleasm/disks/DISK1" is not shared on all nodes-Cause:-Action:
Ignore this error and continue the installation. When the first node is running root. sh script, the data asm volume group is successfully created, but the second and third nodes are running root. sh, the following error is reported:

Mounting Disk Group DATA failed with the following message:
ORA-15032: not all alterations saved med
ORA-15017: diskgroup "DATA" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"
ORA-15080: synchronous I/O operation to a disk failed

Related Article

E-Commerce Solutions

Leverage the same tools powering the Alibaba Ecosystem

Learn more >

Apsara Conference 2019

The Rise of Data Intelligence, September 25th - 27th, Hangzhou, China

Learn more >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.