求助!!2台数据库安装RAC,所做的asmdisk没有实现共享
给2台数据库服务器安装RAC,都是红帽6.064位的系统通过udev的方式来做asmdisk,一共做了6个,分别是asmdisk1至asmdisk6,容量分别是2.4T 2.4T 2.4T 300G 300G 300G
在安装grid,到选择asm disk group的时候,数据库服务器1只能看到asmdisk3 和asmdisk5
尝试在另外一台数据库服务器上安装grid的时候发现,到选择asm disk group的时候,数据库服务器2能够看到asmdisk1,asmdisk2,asmdisk4,asmdisk6
由此判断2台数据库服务器没有实现共享:'( :'( :'(
multipath.conf文件和99-oracle-asmdevices.rules文件都检查了好多遍了,应该没有什么问题
求大神帮忙分析下问题出在哪里啊:Q :Q :Q
2楼我会贴出两个配置文件的详情 回复 1# 洋洋乐悠悠
multipath.conf
user_friendly_names yes
}
blacklist {
devnode "^sda"
}
defaults {
polling_interval 30
failback immediate
no_path_retry 5
rr_min_io 100
path_grouping_policy failover
path_checker tur
user_friendly_names yes
}
multipaths {
multipath {
wwid 360080e5000320d60000003a75306c22c
alias mpatha
path_selector "round-robin 0"
}
multipath {
wwid 360080e500032057c0000030f5306c227
alias mpathb
path_selector "round-robin 0"
}
multipath {
wwid 360080e500032057c00000393530bc27c
alias mpathc
path_selector "round-robin 0"
}
multipath {
wwid 360080e5000320d6000000401530bc24e
alias mpathd
path_selector "round-robin 0"
}
multipath {
wwid 360080e500032057c00000395530bc2a0
alias mpathe
path_selector "round-robin 0"
}
multipath {
wwid 360080e5000320d6000000403530bc266
alias mpathf
path_selector "round-robin 0"
}
multipath {
wwid 360080e500032057c000003115306c25a
alias mpathg
path_selector "round-robin 0"
}
multipath {
wwid 360080e5000320d60000003fd530bc208
alias mpathh
path_selector "round-robin 0"
}
multipath {
wwid 360080e5000320d60000003a55306c1f2
alias mpathi
path_selector "round-robin 0"
}
multipath {
wwid 360080e5000320d60000003ff530bc223
alias mpathj
path_selector "round-robin 0"
}
}
device {
vendor "IBM"
product "2145"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
99-oracle-asmdevices.rules
KERNEL=="sdn", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathh", RESULT=="360080e5000320d60000003fd530bc208", NAME="asmdisk1",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdd", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathh", RESULT=="360080e5000320d60000003fd530bc208", NAME="asmdisk1",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdq", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathj", RESULT=="360080e5000320d60000003ff530bc223", NAME="asmdisk2",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdg", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathj", RESULT=="360080e5000320d60000003ff530bc223", NAME="asmdisk2",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdh", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathc", RESULT=="360080e500032057c00000393530bc27c", NAME="asmdisk3",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdr", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathc", RESULT=="360080e500032057c00000393530bc27c", NAME="asmdisk3",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdi", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathd", RESULT=="360080e5000320d6000000401530bc24e", NAME="asmdisk4",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sds", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathd", RESULT=="360080e5000320d6000000401530bc24e", NAME="asmdisk4",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdj", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathe", RESULT=="360080e500032057c00000395530bc2a0", NAME="asmdisk5",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdt", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathe", RESULT=="360080e500032057c00000395530bc2a0", NAME="asmdisk5",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdk", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathf", RESULT=="360080e5000320d6000000403530bc266", NAME="asmdisk6",OWNER="grid",GROUP="asmadmin", MODE="0660"
KERNEL=="sdu", SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/mapper/mpathf", RESULT=="360080e5000320d6000000403530bc266", NAME="asmdisk6",OWNER="grid",GROUP="asmadmin", MODE="0660"
asm做磁盘组的时候前提是都可以找到共享的分区,不知道楼主你通过fdisk 在两个服务器上是否看到的分区信息是否一致 回复 4# dingning239
现在通过fdisk -l在两台数据库服务器上面看到的信息都是一致的,但是最初的时候,fdisk -l 看到的磁盘信息的sdgsde sdf……这些磁盘符不一致,其他的信息都一致
通过99-oracle-asmdevice.rules不是已经将两台服务器的磁盘符都统一了吗?:'( :?:
盘符不一致会有问题,我曾经在做一套生产环境的时候遇到过这样的问题,最好改过来 存储厂商没有配置多路径吗,如果配置了,就不需要这么麻烦了,直接就可以用。
回复 6# dingning239
问题已经解决了:D)
就是因为存储供应商的多路径没有配置,配置完了之后两台数据库服务器fdisk -l看到的信息完全一致了
回复 7# www_xylove
以后不会再犯这样的错误了,一定让存储厂商把多路径配置好了,我再进行下一步工作
主机存储应该有厂商来负责提供,数据库安装技术人员多跟厂商沟通配置,工作就容易做的多了
页:
[1]
2