Best multipath config for Asm disks?

Hi,
I want to install grid 11.2.0.4 on linux with netapp.
Netapp lun needs multipath.
What is the best config?
Actually this is my ocr lun:
360a98045342554d4f3f453274477178 dm-8 NETAPP,LUN
size=3.0G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=4 status=active
| |- 0:0:1:3 sdh 8:112 active ready running
| `- 1:0:1:3 sdp 8:240 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
|- 1:0:0:3 sdl 8:176 active ready running
`- 0:0:0:3 sdd 8:48 active ready running
Thank you

ASMLib does not handle device path failover, which is the purpose of DM multipath. ASM cannot handle seeing the same disk twice. If it does, it will cause an error. There are special considerations when using ASMLib with Multipath and it is required to configure ASMLib to only use the multipath access point:
A single disk can appear three times in a multipath configuration:
The first path to the disk
The second path to the disk
The multipath access point
Configuring Oracle ASMLib on Multipath Disks

Similar Messages

Using udev devices for ASM disk on Linux

Hello all,
I need details related to using udev devices as ASM disk on Linux.
What I want to know is, once i get the list of ASM Disks that are used to create the DiskGroups, based on the path of the Disk (whether /dev/sdj or /dev/dm-3 or /dev/asm_udev_device, /dev/vx/<vxvm-volume>, /dev/<lvm-volume>) how do i get to know if the device type is a udev device?
I want to know an automated process, so that i can script it out to separate out each device easily.
Please let me know if anyone has expertise on using udev devices with Oracle ASM.
I have referred the link but no much details available http://www.oracle.com/technology/products/database/asm/pdf/device-mapper-udev-crs-asm%20rh4.pdf
Further, the behavior of udevinfo command is very different across version of Linux. From Suse 10 onwards, udevadm has to be used instead.
Its confusing to me.
Please help.
~Sumeet.

My installation, ASM On SI
S.O HP-UIx
Disk internal, not SAN
Internal disk configuration for Oracle.
PV Name /dev/dsk/c11t0d0
PV Name /dev/dsk/c11t1d0
PV Name /dev/dsk/c11t2d0
PV Name /dev/dsk/c11t3d0
PV Name /dev/dsk/c11t4d0
PV Name /dev/dsk/c11t6d0
Vg:
/dev/vgora
Lv
/dev/vgora/lvu01 <-- Oracle Bin mounted /u00
/dev/vgora/lvu02 <-- External Archive /u02
In /dev/vgora
brw-r----- 1 root sys 64 0x010001 Mar 8 14:42 lvu01
brw-r----- 1 root sys 64 0x010002 Mar 8 16:15 lvu02
brwxrwxr-x 1 root sys 64 0x010003 Mar 19 14:19 lvasm01
brwxrwxr-x 1 root sys 64 0x010004 Mar 19 14:20 lvasm02
brwxrwxr-x 1 root sys 64 0x010005 Mar 19 14:20 lvasm03
brwxrwxr-x 1 root sys 64 0x010006 Mar 19 14:20 lvasm04
brwxrwxr-x 1 root sys 64 0x010007 Mar 19 14:20 lvasm05
brwxrwxr-x 1 root sys 64 0x010008 Mar 19 14:20 lvasm06
brwxrwxr-x 1 root sys 64 0x010009 Mar 19 14:20 lvasm07
brwxrwxr-x 1 root sys 64 0x01000a Mar 19 14:20 lvasm08
brwxrwxr-x 1 root sys 64 0x01000b Mar 19 14:20 lvasm09
brwxrwxr-x 1 root sys 64 0x01000c Mar 19 14:21 lvasm10
crw-r----- 1 root sys 64 0x010001 Mar 8 14:42 rlvu01
crw-r----- 1 root sys 64 0x010002 Mar 8 16:15 rlvu02
crw-r--r-- 1 root sys 64 0x010000 Mar 8 14:19 group
FOR ASM
crw-rw---- 1 oracle dba 64 0x010003 Mar 19 14:19 rlvasm01
crw-rw---- 1 oracle dba 64 0x010004 Mar 19 14:20 rlvasm02
crw-rw---- 1 oracle dba 64 0x010005 Mar 19 14:20 rlvasm03
crw-rw---- 1 oracle dba 64 0x010006 Mar 19 14:20 rlvasm04
crw-rw---- 1 oracle dba 64 0x010007 Mar 19 14:20 rlvasm05
crw-rw---- 1 oracle dba 64 0x010008 Mar 19 14:20 rlvasm06
crw-rw---- 1 oracle dba 64 0x010009 Mar 19 14:20 rlvasm07
crw-rw---- 1 oracle dba 64 0x01000a Mar 19 14:20 rlvasm08
crw-rw---- 1 oracle dba 64 0x01000b Mar 19 14:20 rlvasm09
crw-rw---- 1 oracle dba 64 0x01000c Mar 19 14:21 rlvasm10
And the problem is:
When i run dbca for create diskgroup, that not recognize the disk.
I will set asm_diskstring with the correctly path.
I try to create a diskgroup from command line, but i see this error.
SQL> create diskgroup DG_DATA_01 external redundancy DISK '/dev/vgora/rlvasm01' ;
create diskgroup DG_DATA_01 external redundancy DISK '/dev/vgora/rlvasm01'
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/dev/vgora/rlvasm01' matches no disks
ORA-15025: could not open disk '/dev/vgora/rlvasm01'
ORA-15059: invalid device type for ASM disk
Additional information: 255

Best workflow config for music DVD

Hey.
I am about to produce a live music DVD with 5.1 surround and wanted to get some opinions on the best workflow for the project to yeild the best end result for amazing audio.
I was going to start in Logic Pro and finish the final mixdown, then finalize between FCP and Soundtrack....then pull it all into DVD SP. I can keep all the tracks separate if that is a useful strategy. Also, the live audio will be 38 separate channels and then pared down for the final mix. The video and editing I am not worried about.....but making sure the final audio mix in mindblowing is still a huge concern to me. Any suggestions?

I'd go with Bias Deck.
Good luck,
CaptM

Best Hardware config for Vivado

Hi,
I would like to set up a good machine for my compagny, to run vivado.
My idea is to use it remotely to discharge my actual machine.
I need yout experience to choose the best configuration.
So, what are the majors criteria i shoud take into consideration ?
Core number, clock speed, brigre, dual port ddr ?
Usual vivado monitoring show me that it doesn't consume a lot of DDR, but
a lot of CPU.
Maby you even have some references ?
Thanks a lot.

Tkanks for advices.
Finally, here is my configuration :
LDLC QS-550+ GOLD PC ALIMENTATION 80+GOLD
1
NOCTUA NH-U12S
1
GSKILL DDR3 16GB (2*8) F3-2400C11D-16GAB
1
ASUS DRW-24F1ST/BLK/B/AS/OEM
1
ASUS Z97-A
1
INTEL BX80646I74790K 4790K REFRESH
1
FRACTAL DESIGN DEFINE R5 BLACK FD-CA-DEF-R5-BK
1
CRUCIAL SSD BX100 250GB SATA2.5” 7MM -
1

Ironport C160-Best practice config for my 2 listeners?

I am trialling an Ironport C160.
I want it to scan inbound and outbound mail. I have configured a public inbound listener for mail from the internet. It is configured to accept all my domains, and forward them to my exchange server. It does LDAP lookups for recpients to ensure they are valid. It uses the Data1 interface on the ip address of the Ironport and also has the hostname ironport.mydomain.com.
What is the recommended way to configure the private outbound listener? I just want it to do simple av scanning, then pass it on to my ASA.
Should I configure a new interface o Data2, and use port 25? If so, what would the hostname be?
Or use the same interface and use port 24 instead?
What are the pros and cons of each setup?

Please note that you can add your Exchange server IP address into RELAYLIST or any sender group with RELAYED mail flow policy or mail flow policy with 'Relay' connection behavior. Add IronPort listener iP as smart host on Exchange server. All emails from Exchange server will then be treated as outgoing emails and envelope recipient address will not be checked against LDAP.
Most of my customers simply use one listener for both incoming and outgoing emails. You can choose to have multiple listeners for incoming (e.g. Different domains want to have their own MX IP addresses, sender groups for whitelist, greylist, blacklist domain/IP ranges) and outgoing emails (e.g. Not adding 'Received' header for outgoing listener for security reason).
Please note that there is a restriction that you cannot configure IP addresses on same network range on different physical interfaces on IronPort.
You can also configure multiple IP interfaces or interface groups on IronPort such that you can deliver emails for different domains, normal or urgent, management or marketing or other emails by different IP addresses or IP range.

ASM Disk preparation for Datafiles and FRA in Oracle 10g RAC Inst

Dear Friends,
Please clarify wheteher the below method is correct to confiure ASM disks for Datafiles and FRA
Partitions provided by IT team for OCR and Voting Disk
/dev/sda1 - 150 GB (For +DATA)
/dev/sda2 - 100 GB (For +FRA)
OS : RHEL 5.6 (64 Bit)
kernel version = 2.6.18-238.el5
Steps:(Node1)
1) Install the RPM's for ASM
rpm -Uvh oracleasm-support-2.1.7-1.el5.x86_64.rpm
rpm -Uvh oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm
rpm -Uvh oracleasmlib-2.0.4-1.el5.x86_64.rpm
2) Configure ASM
/etc/init.d/oracleasm configure
Default user to own the driver interface []: oracle
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
3) Cretae ASM Disk
/etc/init.d/oracleasm createdisk DISK1 /dev/sda1
/etc/init.d/oracleasm createdisk DISK2 /dev/sda2
4)/etc/init.d/oracleasm status
5)/etc/init.d/oracleasm scandisks
6)/etc/init.d/oracleasm listdisks
7) Nothing to perform on Node2
8) In dbca choose ASM and map the DISK1 for datafiles and DISK2 for FRA
Please confirm the above steps are right?if not please clarify
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?
Please refer any document / Metalink ID for the above complete process
Can i have ASM and oracle DB binary in the same home
Regards,
DB

user564706 wrote:
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?for asm disk created with oracleasm discovery path variable is ORCL:*
Please refer any document / Metalink ID for the above complete processhttp://docs.oracle.com/cd/B19306_01/install.102/b14203/storage.htm#BABIFHAB
Can i have ASM and oracle DB binary in the same homeyes. unless you want job role seperation or plan to run multiple versions of oracle homes
>
Regards,
DB

What's the best Mac Pro config for Fireworks?

What's the best Mac config for Fireworks?
I can pretty much get whatever Mac I want at work... My boss is sick and tired of watching Fireworks crash all the time... I figure a hefty processor and lots of RAM and maybe a SSD will help…
I should get a Mac Pro right? Which processor?
• Two 2.40GHz 6-Core Intel Xeon processors (12 cores)
• Two 2.66GHz 6-Core Intel Xeon processor (12 cores)
• Two 3.06GHz 6-Core Intel Xeon (12 cores)
Should I get 24GB RAM?? Or is that overkill?
I'll get a 2TB serial hard drive…
I should get a 512 GB solid state drive offered by Apple right?
Or is it possible to get a larger better 3rd party SSD?
And then maybe two 21" Displays… Two 27s seems a little much… or does it?
Thanks in advance.

Oh and what about video cards? Or is Apple's default ok? (I'm not doing hard core PhotoShop retouching or anything).

BEST CONFIG FOR EDITING

Hello i have adobe premiere CC with imac, pegasus RAID 4 and external SSD hardrive 512Go. What is the best performance config for : Media temp files, rush, application ?
Thank you

Read all the articles at Tweakers Page

Issue for choosing disk from managed ASM

Hello All,
Oracle Grid Infrastructure installation(11gR2) is in progress, I am not being able to select disk from managed asm disk group, details are as listed below:
uname -a
Linux hostname.host.com 2.6.18-194.el5 #1 SMP Mon Mar 29 22:10:29 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
createdisk for ASM disk group for following disks have been completed:
ASMDATA1
ASMDATA21
ASMDATA22
OCR_VOTE01
OCR_VOTE02
OCR_VOTE03
# oracleasm status
Checking if ASM is loaded: yes
Checking if /dev/oracleasm is mounted: yes
# oracleasm listdisks
ASMDATA1
ASMDATA21
ASMDATA22
OCR_VOTE01
OCR_VOTE02
OCR_VOTE03
$./runcluvfy.sh comp nodereach -n devrac1,devrac2 -verbose
Pre-check for cluster services setup was successful on all the nodes.
$./runcluvfy.sh stage -pre crsinst -n devrac1,devrac2 -verbose
Pre-check for cluster services setup was successful.
$./runcluvfy.sh comp nodecon -n devrac1,devrac2 -verbose
Verification of node connectivity was successful.
$./runcluvfy.sh comp sys -n devrac1,devrac2 -p crs -osdba crs -orainv oinstall
Verification of system requirement was successful.
$./runInstaller
INSTALLATION OPTION: Install and Confgiure Grid Infrastructure for a Cluster
INSTALLATION TYPE: Advanced Installation
PRODUCT lANGUAGE: English
GRID PLUG AND PLAY:
SCAN/GNS configuration:
     cluster Name: devrac1
     SCAN Name: scan.devrac1.domain.company.net
     SCAN Port: 1521
     GNS sub Domain: devrac1.domain.company.net
     GNS VIP Address: 192.168.112.32
CLUSTER NODE INFORMATION
     Hostname: devrac1.domain.company.net,      Hostname: devrac1.domain.company.net
     Virtual IP Name: AUTO,AUTO
     SSH Connectivity: PASS
NETWORK INTERFACE USAGE
     Interface Name:eth0, eth1
     Subnet: 192.168.112.0,10.10.10.0
     Interface Type: Public, Private
STORAGE OPTION: ASM
CREATE ASM DISK GROUP
     DiskGroupname:ORCLDATA
     Redundancy: External
     If Candidate Disks is the option, does't list any disk path.
     If All Disks is the option, list all disks configured for ASM but couldn't check any disk path.
     When we click on "Next" button, following error message would be seen:
          [INS-30507] Empty ASM disk group.
How can I select disk from managed ASM disk group here at this position? What I have missed in my installation for Oracle Grid Infrastructure?
Thanks in advance.
Regards,
Suresh Gautam

Hello Harish,
I don't think that there is issue of discovery string as I can see list of all disks path for ASM, but couldn't include(checked) listed disks for new ASM disk group. I couldn't see any option to trace for OUI while providing configuration for setup, it may trace the information when it starts installation. Please, correct me if I am wrong.
Configuration of /etc/sysconfig/oracleasm is as follows:
ORACLEASM_ENABLED=true
ORACLEASM_UID=oracle
ORACLEASM_GID=oinstall
ORACLEASM_SCANBOOT=true
ORACLEASM_SCANORDER=""
ORACLEASM_SCANEXCLUDE=""
How scan order can resut such a issue during installation? I couldn't understand.
Anyway, I did modification in /etc/sysconfig/oracleasm as you have suggested, then reinitiated installation process after system reboot, modified parameters are listed below for your reference:
ORACLEASM_SCANORDER="emcpower sd"
ORACLEASM_SCANEXCLUDE="sda sdb sdc sdd sde sdf sdg"
BUT COULDN'T RESOLVE THE ISSUE.
output of "fdisk -l" is as follows, it can give you additional information:
========================================================================
# fdisk -l
Disk /dev/sda: 72.9 GB, 72999763968 bytes
255 heads, 63 sectors/track, 8875 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 2053 16386300 82 Linux swap / Solaris
/dev/sda3 2054 8875 54797715 83 Linux
Disk /dev/sdb: 288.1 GB, 288161071104 bytes
255 heads, 63 sectors/track, 35033 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 35033 281402541 83 Linux
Disk /dev/sdc: 287.7 GB, 287762808832 bytes
255 heads, 63 sectors/track, 34985 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 34985 281016981 83 Linux
Disk /dev/sdd: 288.5 GB, 288559333376 bytes
255 heads, 63 sectors/track, 35082 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 1 1217 9775521 83 Linux
/dev/sdd2 1218 2434 9775552+ 83 Linux
/dev/sdd3 2435 3651 9775552+ 83 Linux
/dev/sdd4 3652 35082 252469507+ 83 Linux
Disk /dev/sde: 288.1 GB, 288161071104 bytes
255 heads, 63 sectors/track, 35033 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 1 35033 281402541 83 Linux
Disk /dev/sdf: 287.7 GB, 287762808832 bytes
255 heads, 63 sectors/track, 34985 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdf1 1 34985 281016981 83 Linux
Disk /dev/sdg: 288.5 GB, 288559333376 bytes
255 heads, 63 sectors/track, 35082 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdg1 1 1217 9775521 83 Linux
/dev/sdg2 1218 2434 9775552+ 83 Linux
/dev/sdg3 2435 3651 9775552+ 83 Linux
/dev/sdg4 3652 35082 252469507+ 83 Linux
Disk /dev/emcpowera: 288.1 GB, 288161071104 bytes
255 heads, 63 sectors/track, 35033 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/emcpowera1 1 35033 281402541 83 Linux
Disk /dev/emcpowerb: 287.7 GB, 287762808832 bytes
255 heads, 63 sectors/track, 34985 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/emcpowerb1 1 34985 281016981 83 Linux
Disk /dev/emcpowerc: 288.5 GB, 288559333376 bytes
255 heads, 63 sectors/track, 35082 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/emcpowerc1 1 1217 9775521 83 Linux
/dev/emcpowerc2 1218 2434 9775552+ 83 Linux
/dev/emcpowerc3 2435 3651 9775552+ 83 Linux
/dev/emcpowerc4 3652 35082 252469507+ 83 Linux
========================================================================
Any kind of follow up will be highly appriciated.
Regards,
Suresh Gautam

Please Help - When I try to add ASM Disk to ASM Diskgroup it crashes Server

We are using a Pillar SAN and have LUNS Created and are using the following multipath device: (I'm a DBA more then anything else... but I am rather familiar with linux .... SAN Hardware not so much)
Device Size Mount Point
/dev/dpda1 11G /u01
The Above device is working fine... Below are the ASM Disks being Created
Device Size Oracle ASM Disk Name
/dev/dpdb1 198G ORCL1
/dev/dpdc1 21G SIRE1
/dev/dpdd1 21G CART1
/dev/dpde1 21G SRTS1
/dev/dpdf1 21G CRTT1
I try to create to the first ASM Disk
/etc/init.d/oracleasm createdisk ORCL1 /dev/dpdb1
Marking disk "ORCL1" as an ASM disk: [FAILED]
So I check the oracleasm log:
#cat /var/log/oracleasm
Device "/dev/dpdb1" is not a partition
I did some research and found that this is a common problem with multipath devices and to work around it you have to use asmtool
# /usr/sbin/asmtool -C -l /dev/oracleasm -n ORCL1 -s /dev/dpdb1 -a force=yes
asmtool: Device "/dev/dpdb1" is not a partition
asmtool: Continuing anyway
now I scan and list the disks
# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
# /etc/init.d/oracleasm listdisks
ORCL1
Here is whats going on in /var/log/messages when I run the oracleasm scandisks command
# date
Fri Aug 14 13:51:58 MST 2009
# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
cat /var/log/messages | grep "Aug 14 13:5"
Aug 14 13:52:06 seer kernel: dpdb: dpdb1
Aug 14 13:52:06 seer kernel: dpdc: dpdc1
Aug 14 13:52:06 seer kernel: dpdd: dpdd1
Aug 14 13:52:06 seer kernel: dpde: dpde1
Aug 14 13:52:06 seer kernel: dpdf: dpdf1
Aug 14 13:52:06 seer kernel: dpdg: dpdg1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: printk: 30 messages suppressed.
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: sda : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sda : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: Dev sda: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdb: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdb: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdb: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdb: sdb1
Aug 14 13:52:06 seer kernel: SCSI device sdc: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdc: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdc: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdc: sdc1
Aug 14 13:52:06 seer kernel: SCSI device sdd: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdd: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdd: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdd: sdd1
Aug 14 13:52:06 seer kernel: SCSI device sde: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sde: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sde: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sde: sde1
Aug 14 13:52:06 seer kernel: SCSI device sdf: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdf: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdf: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdf: sdf1
Aug 14 13:52:06 seer kernel: SCSI device sdg: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdg: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdg: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdg: sdg1
Aug 14 13:52:06 seer kernel: SCSI device sdh: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdh: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdh: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdh: sdh1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sdi, logical block 0
Aug 14 13:52:06 seer kernel: sdi : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdi : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdi: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdi: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdi: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdi:end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer last message repeated 4 times
Aug 14 13:52:06 seer kernel: Dev sdi: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdj: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdj: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdj: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdj: sdj1
Aug 14 13:52:06 seer kernel: SCSI device sdk: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdk: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdk: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdk: sdk1
Aug 14 13:52:06 seer kernel: SCSI device sdl: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdl: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdl: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdl: sdl1
Aug 14 13:52:06 seer kernel: SCSI device sdm: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdm: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdm: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdm: sdm1
Aug 14 13:52:06 seer kernel: SCSI device sdn: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdn: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdn: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdn: sdn1
Aug 14 13:52:06 seer kernel: SCSI device sdo: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdo: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdo: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdo: sdo1
Aug 14 13:52:06 seer kernel: SCSI device sdp: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdp: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdp: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdp: sdp1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: sdq : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdq : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdq: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdq: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdq: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdq:end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer last message repeated 5 times
Aug 14 13:52:06 seer kernel: Dev sdq: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdr: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdr: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdr: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdr: sdr1
Aug 14 13:52:06 seer kernel: SCSI device sds: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sds: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sds: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sds: sds1
Aug 14 13:52:06 seer kernel: SCSI device sdt: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdt: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdt: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdt: sdt1
Aug 14 13:52:06 seer kernel: SCSI device sdu: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdu: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdu: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdu: sdu1
Aug 14 13:52:06 seer kernel: SCSI device sdv: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdv: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdv: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdv: sdv1
Aug 14 13:52:06 seer kernel: SCSI device sdw: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdw: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdw: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdw: sdw1
Aug 14 13:52:06 seer kernel: SCSI device sdx: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdx: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdx: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdx: sdx1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: sdy : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdy : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdy: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdy: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdy: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdy:end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer last message repeated 5 times
Aug 14 13:52:06 seer kernel: Dev sdy: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdz: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdz: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdz: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdz: sdz1
Aug 14 13:52:06 seer kernel: SCSI device sdaa: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdaa: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdaa: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdaa: sdaa1
Aug 14 13:52:06 seer kernel: SCSI device sdab: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdab: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdab: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdab: sdab1
Aug 14 13:52:06 seer kernel: SCSI device sdac: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdac: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdac: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdac: sdac1
Aug 14 13:52:06 seer kernel: SCSI device sdad: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdad: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdad: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdad: sdad1
Aug 14 13:52:06 seer kernel: SCSI device sdae: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdae: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdae: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdae: sdae1
Aug 14 13:52:06 seer kernel: SCSI device sdaf: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdaf: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdaf: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdaf: sdaf1
Aug 14 13:52:06 seer kernel: scsi_wr_disk: unknown partition table
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdy, sector 0
Here's some extra info:
# /sbin/blkid | grep asm
/dev/sdc1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sdk1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sds1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sdaa1: LABEL="ORCL1" TYPE="oracleasm"
/dev/dpdb1: LABEL="ORCL1" TYPE="oracleasm"
I have learned that by excluding devices in the oracleasm configuration file I eliminate those I/O errors in /var/log/messages
# cat /etc/sysconfig/oracleasm
# This is a configuration file for automatic loading of the Oracle
# Automatic Storage Management library kernel driver. It is generated
# By running /etc/init.d/oracleasm configure. Please use that method
# to modify this file
# ORACLEASM_ENABELED: 'true' means to load the driver on boot.
ORACLEASM_ENABLED=true
# ORACLEASM_UID: Default user owning the /dev/oracleasm mount point.
ORACLEASM_UID=oracle
# ORACLEASM_GID: Default group owning the /dev/oracleasm mount point.
ORACLEASM_GID=oinstall
# ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
ORACLEASM_SCANBOOT=true
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="dp sd"
# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE="sdc sdk sds sdaa sda"
# ls -la /dev/oracleasm/disks/
total 0
drwxr-xr-x 1 root root 0 Aug 14 10:47 .
drwxr-xr-x 4 root root 0 Aug 13 15:32 ..
brw-rw---- 1 oracle oinstall 251, 33 Aug 14 13:46 ORCL1
Now I can go into dbca to create the ASM instance, which starts up fine... create a new diskgroup, I see ORCL1 as a provision ASM disk I select it ... Click OK
CRASH!!! Box hangs have to reboot it....
I have gotten myself to exactly the same point right before clicking OK and here is what is in the ASM alertlog so far
Fri Aug 14 14:42:02 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.1.0/db_1/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =0
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile /u01/app/oracle/product/11.1.0/db_1/dbs/spfile+ASM.ora
System parameters with non-default values:
large_pool_size = 12M
instance_type = "asm"
diagnostic_dest = "/u01/app/oracle"
Fri Aug 14 14:42:04 2009
PMON started with pid=2, OS id=3300
Fri Aug 14 14:42:04 2009
VKTM started with pid=3, OS id=3302 at elevated priority
VKTM running at (20)ms precision
Fri Aug 14 14:42:04 2009
DIAG started with pid=4, OS id=3306
Fri Aug 14 14:42:04 2009
PSP0 started with pid=5, OS id=3308
Fri Aug 14 14:42:04 2009
DSKM started with pid=6, OS id=3310
Fri Aug 14 14:42:04 2009
DIA0 started with pid=7, OS id=3312
Fri Aug 14 14:42:04 2009
MMAN started with pid=8, OS id=3314
Fri Aug 14 14:42:04 2009
DBW0 started with pid=9, OS id=3316
Fri Aug 14 14:42:04 2009
LGWR started with pid=6, OS id=3318
Fri Aug 14 14:42:04 2009
CKPT started with pid=10, OS id=3320
Fri Aug 14 14:42:04 2009
SMON started with pid=11, OS id=3322
Fri Aug 14 14:42:04 2009
RBAL started with pid=12, OS id=3324
Fri Aug 14 14:42:04 2009
GMON started with pid=13, OS id=3326
ORACLE_BASE from environment = /u01/app/oracle
Fri Aug 14 14:42:04 2009
SQL> ALTER DISKGROUP ALL MOUNT
Fri Aug 14 14:42:41 2009
At this point I don't want to click the OK until I am sure someone is in the office to reboot the machine manually if I do hang it again.... I hung it twice yesterday, however I did not have the devices excluded in the oracleasm configuration file as i do now
Edited by: user10193377 on Aug 14, 2009 3:23 PM
Well Clicking OK hun it again and I am waiting to get back into it, to see what new information might be gleened
Does anyone have any ideas on what to check or where to look????? Will update more once I can log back in

Hi Mark,
It looks like something is not correct with your raw device partition based on the error messages:
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
It could be a number of things. I would check with your vendor and Oracle support to see if the multipath software drive is supported and if there is a potential workaround for ASM. Sorry this is not quite the solution, but its what jumps to mind based on issues with multipath software and storage vendors for ASM with Linux and Oracle. Have you checked the validation matrix available on Metalink?
Cheers,
Ben

Oracleasm cannot find asm disks on boot

Hello!
RAC 11.2.0.2 on SLES10.
I have configured asmlib on a RAC system (multipath configured) and everything worked as a charm before booting node 2 in the cluster. Problem is that after reboot of node 2 i cannot see my asm disks anymore on that node. This only happens on node 2. I dont have this issue after rebooting node 1. However, if i do a manually "scandisks" on node 2 it sees the disks again and the cluster starts successfully..
I cannot see any difference between the two nodes.. the asmlib rpm's matches the kernel version.
oracle@prod2:~> uname -a
Linux prod2 2.6.16.60-0.54.5-smp #1 SMP Fri Sep 4 01:28:03 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux
oracle@prod2:~> rpm -qa |grep oracleasm
oracleasm-support-2.1.4-1.SLE10
oracleasm-2.6.16.60-0.54.5-smp-2.0.5-1.SLE10
oracleasmlib-2.0.4-1.SLE10/etc/sysconfig/oracleasm looks like this:
# This is a configuration file for automatic loading of the Oracle
# Automatic Storage Management library kernel driver. It is generated
# By running /etc/init.d/oracleasm configure. Please use that method
# to modify this file
# ORACLEASM_ENABELED: 'true' means to load the driver on boot.
ORACLEASM_ENABLED=true
# ORACLEASM_UID: Default user owning the /dev/oracleasm mount point.
ORACLEASM_UID=oracle
# ORACLEASM_GID: Default group owning the /dev/oracleasm mount point.
ORACLEASM_GID=dba
# ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
ORACLEASM_SCANBOOT=true
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="dm"
# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE="sd"I would be grateful if anyone out there can shed some light on this issue..
Thanks a bunch!

Hi,
I think you need to upgrade your powerpath version. If you are using clariion for your storage.

Create ASM Disk Groups cannot see Disk Path to select during installation

Hello Guys,
I am setting up 2 node RAC on 11gR2 and Linux.
I have configured all the pre-installation steps that are required to run Grid Setup as per my understanding.
I have configure SAN partitions using multipath.
I can see my SAN volume when i query multipath -l
Then i configured the raw partitions by oracleasm. Configured and then created mount points:
/dev/oracleasm/disks/
CRSVOL1 DATAVOL1 FRAVOL1
Later on I created the disks using oracle asm command:
/usr/sbin/oracleasm createdisk CRSVOL1 /dev/mapper/racdbp1 and so on...
I have run /usr/sbin/oracleasm scandisks
Cleaning any stale ASM disks...
Scanning system for ASM disks...
And when i list disk with command /usr/sbin/oracleasm listdisks
it shows the disk like this on both nodes:
CRSVOL1
DATAVOL1
FRAVOL1
BUT during the installation screen when it comes to create ASM Disk Groups It shows nothing in the add disk frame, I cant select the volumes I can list, like i did above.
Any hint please?
Thanks, Imran

Thanks but my problem is very specific. I feel that i have performed all the necessary steps to get complete the step i discussed above. As per different commands all is set. But i am unable to see Disks and Disks Paths during the installation screen. This is another output to verify if the installe user have rights on the asm devices:
[grid@racnode1 mapper]$ cd /dev/oracleasm/disks/
DATAVOL1 ETSCRS1 ETSVOT1 ETSVOT3 FRAVOL1
ETSASM1 ETSCRS2 ETSVOT2 EXTRADM
[grid@racnode1 mapper]$ cd /dev/oracleasm/disks/
[grid@racnode1 disks]$ ls -ltr
total 0
brw-rw---- 1 grid asmadmin 8, 1 Oct 2 16:47 ETSASM1
brw-rw---- 1 grid asmadmin 8, 5 Oct 2 16:47 DATAVOL1
brw-rw---- 1 grid asmadmin 8, 6 Oct 2 16:47 FRAVOL1
brw-rw---- 1 grid asmadmin 8, 7 Oct 2 16:47 ETSVOT1
brw-rw---- 1 grid asmadmin 8, 8 Oct 2 16:47 ETSVOT2
brw-rw---- 1 grid asmadmin 8, 9 Oct 2 16:47 ETSVOT3
brw-rw---- 1 grid asmadmin 8, 10 Oct 2 16:47 ETSCRS1
brw-rw---- 1 grid asmadmin 8, 11 Oct 2 16:47 ETSCRS2
brw-rw---- 1 grid asmadmin 8, 13 Oct 2 16:47 EXTRADM
I will appreciate if you can help me to get through this step... Is there anything else needs to be verified?
Regards, Imran

Multipath.conf for oel 6.4 and oracle zfs appliance

i have a zfs 7320 storage appliance connected via brocade fiber switches to clustered linux servers. one zfs controller with four fiber connections each server has two fiber connections. there are redundant switches so zfs is connected with two fiber connections to each switch and each server is connected one fiber connection to each switch. the zfs appliance manual does not have oel or redhat or any other similar 6.x multipath configuration. oracle support or sales has not been able as of yet to find multipath config for 6.x and suggested i post it here. Since I had issues that seem to be resolved with new zfs appliance software I want to verify my multipath config before i put the unit back in production, I would feel much better with a known good config.
This is what is in the manual for 5.x linux:
device
vendor "SUN"
product "Sun Storage 7310" or "Sun Storage 7410" (depending on storage system)
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
hardware_handler "0"
path_grouping_policy group_by_prio
failback immediate
no_path_retry queue
rr_min_io 100
path_checker tur
rr_weight uniform
This is what seems to work with 6.x:
device {
vendor "SUN"
product "ZFS Storage 7320"
getuid_callout "/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/%n"
prio alua
hardware_handler "0"
path_grouping_policy group_by_prio
failback immediate
no_path_retry queue
rr_min_io 100
path_checker tur
rr_weight uniform
}

Nice to see a proper redundant storage fabric layer for once on OTN. ;-)
We've been in a similar position using multipath with a custom storage layer (Infiniband based). Like you we hunted for a best-match config - and then stress tested the fabric layer using fio (Flexible I/O Tester). And don't forget to pull some fibre cables, or shutdown/powerdown one of the fibre channel switches, while fio tests are running.

Error while creating asm disk group

i am trying to convert my database SRAVAN as an ASM instance.
so do i need to set ORACLE_SID=+ASM???? r else it wil be SRAVAN??
I WAS ENDED UP WITH FOLLOWING ERRORS WHILE CREATING DISK GROUP.
guyz please do help me
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK '/u04/app/oracle/product/asmdisks/disk1'
5 FAILGROUP ctlr2
6 DISK '/u04/app/oracle/product/asmdisks/disk2';
CREATE DISKGROUP dgroup1
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk2' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk2'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk1' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk1'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
[oracle@sierra200 dbs]$ cd /u04/app/oracle/product/asmdisks
[oracle@sierra200 asmdisks]$ ls -ltr
total 205008
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:42 disk1
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:47 disk2
Thanks & Regards
Sravan Dalavai

Looks like you are asking ASM to use plain files. Have you used the Device Loopback (losetup) a d made the emulate raw devices?
http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_20.shtml

Soft I/O error in ASM disk volume when using iostat commmand

Dear All,
We are having 2 node 11g rac/sun solaris 10/ASM storage, when we using iostat in node 2 getting soft I/O error keep on increasing.
s/w h/w trn tot device
*82 0 0 82 c4t600A0B80006766CD000003DF4B20A7FCd0*
s/w h/w trn tot device
0 0 0 0 md/d10
0 0 0 0 md/d11
0 0 0 0 md/d12
0 0 0 0 md/d20
0 0 0 0 md/d21
0 0 0 0 md/d22
0 0 0 0 md/d30
0 0 0 0 md/d31
0 0 0 0 md/d32
0 0 0 0 md/d40
0 0 0 0 md/d41
0 0 0 0 md/d42
0 0 0 0 md/d50
4 0 2 6 c0t0d0
0 0 0 0 c1t2d0
0 0 0 0 c1t0d0
0 0 0 0 c1t4d0
0 0 0 0 c1t1d0
2 0 0 2 c3t203200A0B86766CDd31
0 0 0 0 c4t600A0B80006766CD000003E14B20C891d0
40 0 0 40 c4t600A0B80006766CD000003DF4B20A7FCd0
0 0 0 0 c4t600A0B80006766CD000003DD4B20A57Fd0
0 0 0 0 c4t600A0B80006766CD000003C34B0D2D31d0
2 0 0 2 c4t600C0FF0000000000859635DB0097B00d0
2 0 0 2 c4t600C0FF000000000085963724A889B00d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F02d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F01d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F00d0
2 0 0 2 c2t202200A0B86766CDd31
0 0 0 0 c4t600A0B80006766CD000052274FD0B057d0
1 0 0 1 c4t600C0FF0000000000859635DB0097B02d0
2 0 0 2 c4t600C0FF000000000085963565767D300d0
2 0 0 2 c4t600C0FF00000000008596326C5F42901d0
1 0 0 1 c4t600C0FF00000000008596326C5F42900d0
1 0 0 1 c2t203300A0B86766CDd31
0 0 0 0 proddb2.zakathouse.org:vold(pid672)
please advice me how to troubshoot and fix this error
Thanks & Regards

Hi,
I suggest to have a look at following script which is provided by oracle to monitor IO.
ASMIOSTAT Script to collect iostats for ASM disks [ID 437996.1]
Further this i have questions
1) Are you logged in asm sysasm? Make sure that you have proper rights
2) Did you check the liveness of asm instance? Make sure its up and functional also check the asm alert.log for awareness.
Hope this helps

Best multipath config for Asm disks?

Similar Messages

Maybe you are looking for