Oracle ASM Disk Name Lenght Limit

Hi,
Does anyone know wheter or not oracleasm has a maximum disk name lenght limit, I have a situation where "#oracleasm listdisks" shows the same name for 5 of my disks and seems to have truncated the last character from the disk name.
So, now my ASM Diskgroup is not starting up because it sees that there are "missing" disks, but they are not missing, they are just listed with the same Disk Name.
Commands used to create the disks:
oracleasm createdisk RAC_DATA146_500GB_DISK001 /dev/emcpowerek1
oracleasm createdisk RAC_DATA146_500GB_DISK002 /dev/emcpowerem1
oracleasm createdisk RAC_DATA146_500GB_DISK003 /dev/emcpowerej1
oracleasm createdisk RAC_DATA146_500GB_DISK004 /dev/emcpowerel1
oracleasm createdisk RAC_DATA146_500GB_DISK005 /dev/emcpowerei1
Now, see the output when I do a querydisk:
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerek1
Disk "/dev/emcpowerek1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerem1
Disk "/dev/emcpowerem1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerej1
Disk "/dev/emcpowerej1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerel1
Disk "/dev/emcpowerel1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
[root@birac01 ~]# oracleasm querydisk /dev/emcpowerei1
Disk "/dev/emcpowerei1" is marked an ASM disk with the label "RAC_DATA146_500GB_DISK00"
So, it looks like the version of oracleasm that I'm running has a name lenght limit? IS this possible?
[root@birac01 ~]# rpm -qa | grep oracleasm
oracleasm-support-2.0.3-1
oracleasm-2.6.9-55.ELsmp-2.0.3-1
oracleasmlib-2.0.2-1
Can anyone please help?
Regards
Stephan
Edited by: user1675141 on Mar 22, 2011 2:10 AM

Oracleasmlib does not seem to advertise such information. As such it might be a poor design that it is not verifiying user input.
According to http://download.oracle.com/docs/cd/E11882_01/install.112/e17212/storage.htm#CWLIN294
+"The disk names that you specify can contain uppercase letters, numbers, and the underscore character. They must start with an uppercase letter."+
The Oracle ASM assistant documentation shows:
+"A volume name of Oracle ASM can be a maximum of 11 alphanumeric characters; dashes are not allowed. The first character must be alphabetic"+
Why are you using such long volume and device names in first place? I would abbreviate the names and make them shorter. The url above will also show you information about configuring multipath and udev.
You could try to query device names using:
/etc/init.d/oracleasm querydisk -p VOL1
and rename volumes using:
/etc/init.d/oracleasm renamedisk /dev/sdb1 VOL1
Edited by: Dude on Mar 22, 2011 5:19 AM

Similar Messages

  • Change ASM DISK NAME in 11.2 version

    Hi,
    Is it possible to change ASM DISK NAME for example in diskgroup DATA01. I added disk without NAME, and system-choosen NAME is allocated. Can I set it to e.g., ORCL:DATA09 . Currently its DATA09_009.
    Please suggest your views.
    Thanks a lot.
    Best Regards                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    You can change the label of disk using oracleasm renamedisk; oracle discourages it
    I will changing the label of disk from CLONE1 to CLONE1a and CLONE2 to CLONE2a of diskgroup CLONE
    SQL> col disk_number for 99
    SQL> col name for a15
    SQL> col label for a15
    SQL> col path for a30
    SQL> select disk_number,name,label,path from v$asm_disk;
    0 DATA CLONE1 ORCL:CLONE1
    1 LOGS CLONE2 ORCL:CLONE2
    ASMCMD> lsdsk -G CLONE
    Path
    ORCL:CLONE1
    ORCL:CLONE2
    ASMCMD> umount CLONE
    [root@otest]# /etc/init.d/oracleasm force-renamedisk CLONE1 CLONE1a
    Renaming disk "CLONE1" to "CLONE1a": [  OK  ]
    [root@otest]# /etc/init.d/oracleasm force-renamedisk CLONE2 CLONE2a
    Renaming disk "CLONE2" to "CLONE2a": [  OK  ]
    ASMCMD> mount CLONE
    ASMCMD> lsdsk -G CLONE
    Path
    ORCL:CLONE1A
    ORCL:CLONE2A
    select disk_number,name,label,path from v$asm_disk;SQL> SQL> SQL> SQL>
    0 DATA CLONE1A ORCL:CLONE1A
    1 LOGS CLONE2A ORCL:CLONE2A
    Edited by: vlethakula on Jan 18, 2013 11:48 AM
    Edited by: vlethakula on Jan 18, 2013 11:56 AM

  • Oracle ASM Disks Question

    Hi,
    We have two Linux hosts accessing EMC SAN LUNs and we have Oracle ASM Disks created on those devices. Both the Linux Hosts (server1/2)are in once Dell Blade Chassis1 and one of the Server we are planning to move to a different Dell Chassis(2) to have redundency in case of Chassis1 faliure. But if we move one server2 to Chassis2 the HBA WWN Number for the host on the new Dell Chassis2 will change ( WWNs are assigned by Chassis on Dell) and the server2 will loose all the SAN LUNs from EMC Array. I will have to rezone the new server WWNs to storage and pesent the same disks again and rescan the disks which will take couple of reboots. During this period EMC LUNs will not be visible to server2 and I would like to what will happen to ASM disks on the server2 and how to I accomlish this goal? Any detailed steps please? This is a production system with oracle 11g running.
    This is the output of emc powerpath devices (LUNs) which is same on both the hosts.
    [root@server2 ~]# powermt display dev=all | grep emc
    Pseudo name=emcpowerl
    Pseudo name=emcpowerj
    Pseudo name=emcpowerf
    Pseudo name=emcpowerk
    Pseudo name=emcpowerg
    Pseudo name=emcpowerh
    Pseudo name=emcpowerm
    Pseudo name=emcpoweri
    [root@server2 ~]#
    This are the ASM disks on both the hosts:
    [root@server2 ~]# oracleasm listdisks
    DATA01_F1
    DATA01_G1
    DATA01_H1
    DATA01_I1
    FRA01_L1
    LOG01_J1
    LOG01_K1
    [root@server2 ~]#
    Thanks in advance.

    808306 wrote:
    But if we move one server2 to Chassis2 the HBA WWN Number for the host on the new Dell Chassis2 will change ( WWNs are assigned by Chassis on Dell) and the server2 will loose all the SAN LUNs from EMC Array.This does not sound correct to me. WWNs are global - not local. If the WWN is foo123 on server1 for EMC LUN1, why would it not also be foo123 on server2 for EMC LUN1? When you move to server3 or install server3, why would EMC LUN1 not have a WWN of foo123 on server3?
    I will have to rezone the new server WWNs to storage and pesent the same disks again and rescan the disks which will take couple of reboots. Using Powerpath perhaps - using multipath, not. New devices (LUNs) can be made visible by the kernel my refreshing multipath - no reboot required. If existing LUNs are going to be changed - yes, a single reboot will be needed. But not multiple (unless you have a driver issue with stale connections not being reset on the storage server side).
    This is the output of emc powerpath devices (LUNs) which is same on both the hosts.We dropped Powerpath a long time ago. There were compatibility issues between it and AsmLib kernel drivers. Powerpath taints the Linux kernel and limits kernel upgrade flexibility. I refuse to run it on our new clusters. I use multipath instead - the very same s/w used by some of the largest clusters (with Pentabyte storage) in the world. The comfort factor using Open Source drivers (and certified for that kernel version) is significantly higher than installing 3rd party kernel driver binaries - and having to deal with a 2nd party when it comes to o/s and kernel support.

  • Oracle ASM disk group

    Hi,
    Having a multiple Oracle ASM disk group is more beneficial for Oracle database? if no why? if yes why?
    Any metalink note if have.
    thanks

    Any metalink note do you refer?What is your database version?
    Please see these docs.
    11g ASM New Feature [ID 429098.1]
    ASM 11g New Features - How ASM Disk Resync Works. [ID 466326.1]
    Thanks,
    Hussein

  • Oracle ASM disk to WWID

    Anyone know of a way to take an Oracle ASM disk (i.e. oracle ORCL:TEST_ASMDATA006) and finding the wwid of the underlying LUN? We are running 11.2.0.3 EE on redhat 5.8 with asmlib installed. Our current thought is we can take major minor and back track to multipath.conf file which we manually maintain when we add a lun. Would prefer a more direct way to do this if there is one.
    Thanks
    Steve

    You can query the physical device of a ASMLib volume using:
    /etc/init.d/oracleasm querydisk -p ASMVOL
    Then query the WWID:
    scsi_id -g -u -s /block/sda

  • 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

  • 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

  • How to map ASM disk path to physical disk on AIX?

    Hi Everyone,
    I am working on a plug-in for Oracle Enterprise Manager 10gR2 on AIX 5.3 which provides monitoring of storage arrays and supports ASM databases in addition to the 'emrep' database. One of the metric of that plug-in is populated by the result from a korn shell script. The script directly runs on the AIX host (connected to the storage array by FC cables via HBA ports) and retrieves the mapping for -- Physical disk - Logical Disk - LUN - ASM Disk.
    Now, I was able to get the mapping for Physical Disk – Logical Disk – LUN, but could not map ASM Disk. I googled a lot for any clue but did not find the answer to this specific problem.
    Now, I have the list of physical disks used for ASM by the command—
    lspv
    hdisk0 0001c22ac8d664ca rootvg active
    hdisk1 0001c22aa51f496a Oracle active
    hdisk2 0001c22ac478263a scratch active
    hdisk3 0001c22ac472549a Oracle active
    hdisk4 0001c22ac4725d6a Oracle active
    hdisk5 none None
    hdisk6 none None
    hdisk7 none None
    hdisk8 none None
    hdisk9 none None
    hdisk10 none None
    hdisk11 none None
    hdisk12 none None
    hdisk13 none None
    hdisk14 none None
    hdisk15 none None
    hdisk16 none None
    The disks hdisk5-16 are ASM disks and there are no PVID’s present.
    I also have the list of ASM disks by the command—
    ls –l /dev | grep oracle
    crw-rw---- 1 oracle dba 22, 6 May 12 00:02 asm_rd10_1a
    crw-rw---- 1 oracle dba 22, 10 Apr 21 07:27 asm_rd10_1b
    crw-rw---- 1 oracle dba 22, 7 May 09 13:53 asm_rd10_1c
    crw-rw---- 1 oracle dba 22, 8 May 09 13:53 asm_rd5_1a
    crw-rw---- 1 oracle dba 22, 4 May 12 00:02 asm_rd5_1b
    crw-rw---- 1 oracle dba 22, 9 Apr 21 07:28 asm_rd5_1c
    crw-rw---- 1 oracle dba 22, 12 May 12 00:02 asm_xbb2_rd10_1a
    crw-rw---- 1 oracle dba 22, 11 Apr 24 07:34 asm_xbb2_rd10_1b
    crw-rw---- 1 oracle dba 22, 13 May 09 13:53 asm_xbb2_rd10_1c
    crw-rw---- 1 oracle dba 22, 16 May 12 00:02 asm_xbb2_rd5_1a
    crw-rw---- 1 oracle dba 22, 14 Apr 24 07:34 asm_xbb2_rd5_1b
    crw-rw---- 1 oracle dba 22, 15 May 09 13:54 asm_xbb2_rd5_1c
    Now I am looking for a way to map these two lists with each other, and had no luck so far.
    Does oracle provide this information somewhere in the OEM installation structure or is there a command in AIX which could give some way to map the ASM disks to the physical disks?
    Any help on this is greatly appreciated. Thanks in advance…
    FYI: ASMLib driver is not present on the system.

    The view you are talking about here gives the ASM DISK NAME (like DGRXBB_0001) and ASM DISK PATH (like /dev/asm_rd_10_1a) and I am already using it, but this is not what I asked in mt original post. If you read carefully, I want to establish a mapping between the ASM DISK PATH (like /dev/asm_rd_10_1a) and the AIX Physical disk (like /dev/hdisk5) and did not find any view giving this info. If you know of some views which could help establish this mapping or some AIX commands or files that could help do this using shell script, it is most welcome

  • Problem with create asm disk group

    Hi all
    I am about configuring ASM, so I have downloaded the Grid infrastructure 11g (32 bit), I have configured and created parameters and directories.
    I runned the installer but get stack at the 3 step where I have to change the discovery path. I have taped as path /dev where I have created 3 partitions sdb1, sdc1 and sdd1.
    Is there any thing should I perform on partitions may be or parameters to set before I go through the installation?
    Thanks for help

    You can use the below link to install ASMLIB:
    http://gssdba.wordpress.com/category/asm/
    REFERANCE : Doc ID 580153.1
    There are two different methods to configure ASM on Linux:
    ASM with ASMLib I/O: This method creates all Oracle database files on raw block devices managed by ASM using ASMLib calls. RAW devices are not required with this method as ASMLib works with block devices.
    ASM with Standard Linux I/O: This method creates all Oracle database files on raw character devices managed by ASM using standard Linux I/O system calls. You will be required to create RAW devices for all disk partitions used by ASM.
    You can download the ASMLIB rpm’s from below URL:
    http://www.oracle.com/technetwork/server-storage/linux/downloads/rhel5-084877.html
    STEP 01: LOG IN AS ROOT USER AND INSTALL THE RPMS
    [root@node1 ASMLIB]# rpm -Uvh oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm \
    > oracleasmlib-2.0.4-1.el5.i386.rpm \
    > oracleasm-support-2.1.8-1.el5.i386.rpm
    warning: oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
    Preparing… ########################################### [100%]
    1:oracleasm-support ########################################### [ 33%]
    2:oracleasm-2.6.18-164.el########################################### [ 67%]
    3:oracleasmlib ########################################### [100%]
    STEP 02: CONFIGURE ASMLIB
    [root@node1 ASMLIB]# /etc/init.d/oracleasm configure
    Configuring the Oracle ASM library driver.
    This will configure the on-boot properties of the Oracle ASM library
    driver. The following questions will determine whether the driver is
    loaded on boot and what permissions it will have. The current values
    will be shown in brackets (‘[]‘). Hitting <ENTER> without typing an
    answer will keep that current value. Ctrl-C will abort.
    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]: y
    Writing Oracle ASM library driver configuration: done
    Initializing the Oracle ASMLib driver: [ OK ]
    Scanning the system for Oracle ASMLib disks: [ OK ]
    STEP 03 :CREATE ASM DISK
    [root@node1 ASMLIB]# /etc/init.d/oracleasm listdisks
    [root@node1 ASMLIB]#
    [root@node1 ~]# /etc/init.d/oracleasm createdisk VOL1 /dev/sdb1
    Marking disk “VOL1″ as an ASM disk: [ OK ]
    [root@node1 ~]# /etc/init.d/oracleasm createdisk VOL2 /dev/sdc1
    Marking disk “VOL2″ as an ASM disk: [ OK ]
    [root@node1 ~]# /etc/init.d/oracleasm createdisk VOL3 /dev/sdd1
    Marking disk “VOL3″ as an ASM disk: [ OK ]
    [root@node1 ~]# /etc/init.d/oracleasm createdisk VOL4 /dev/sde1
    Marking disk “VOL4″ as an ASM disk: [ OK ]
    [root@node1 ~]# /etc/init.d/oracleasm createdisk VOL5 /dev/sdf1
    Marking disk “VOL5″ as an ASM disk: [ OK ]
    [root@node1 ~]# /etc/init.d/oracleasm listdisks
    VOL1
    VOL2
    VOL3
    VOL4
    VOL5
    [root@node1 ~]#

  • ASM Disk

      What types of disks are supported and needed for the oracle ASM
      we are using SAN for shared storage
      can we use a " disk partition " for asm do we require all the disks need to be partitioned with primary partition ty type
      can we use a single disk worth 800 GB partition and divide it into 3 primary and 1 extended partition and on extended create logical partitions and use it for oracle asm
    Can any body Please provide an accurate minimal disk group recommendation for installing an oracle rac 11. 2.0.2.0  standard edition- 64bit with  RHEL- 6 Host

    Oracle documentation says
        create an Oracle ASM disk group using one of the following storage resources:
    Disk PartitionA disk partition can be the entire disk drive or a section of a disk drive. However, the Oracle ASM disk cannot be in a partition that includes the partition table because the partition table would be overwritten.
    Logical Unit Number (LUN)A LUN is a disk presented to a computer system by a storage array. Oracle recommends that you use hardware RAID functionality to create LUNs. Storage hardware RAID 0+1 or RAID5, and other RAID configurations, can be provided to Oracle ASM as Oracle ASM disks.
    Logical VolumeA logical volume is supported in less complicated configurations where a logical volume is mapped to a LUN, or a logical volume uses disks or raw partitions. Logical volume configurations are not recommended by Oracle because they create a duplication of functionality. Oracle also does not recommended using logical volume managers for mirroring because Oracle ASM provides mirroring.
    Network File System (NFS)An Oracle ASM disk group can be created from NFS files, including Oracle Direct NFS (dNFS), as well as whole disks, partitions, and LUNs. The NFS files that are provisioned to a disk group may be from multiple NFS servers to provide better load balancing and flexible capacity planning.Direct NFS can be used to store data files, but is not supported for Oracle Clusterware files. To install Oracle Real Application Clusters (Oracle RAC) on Windows using Direct NFS, you must also have access to a shared storage method other than NFS for Oracle Clusterware files.

  • Add ASM disk in RAC

    Hello everyone,
    We are on 10gR2 ASM.
    The system admin has provided one disk as follows:
    On node-1 (tphsmsd1)
    /dev/rdisk/disk83 CANDIDATE
    On node-2 (tphsmsd2)
    /dev/rdisk/disk77 CANDIDATE
    I've read that paths of ASM disks in RAC may be different.
    When I give "ls -l /dev/rdisk/disk83" gives no such files and vice-versa for disk on node2.
    I don't understand how ASM handles this ? If I add disk (disk83) on node 1 how it's going to get to that disk on node 2 ?
    thanks
    Jitu Keshwani

    Jitu Keshwani wrote:
    I've read that paths of ASM disks in RAC may be different.
    When I give "ls -l /dev/rdisk/disk83" gives no such files and vice-versa for disk on node2.
    I don't understand how ASM handles this ? If I add disk (disk83) on node 1 how it's going to get to that disk on node 2 ?The header label of the disk, identifies the ASM disk name and diskgroup it belongs to. You can hexdump or octaldump the 1st 128 bytes of the device as ascii chars to view the label. The string "+ORCLDISK+" in the header identifies it as an ASM disk. This is then followed by the ASM diskname and then the AM diskgroup it belongs to.
    But there's no reason for not having a consistent and static device name layer across all cluster nodes. Each scsi device has a WWID (World Wide ID)- a unique identifier. This means that the kernel (and kernel drivers) can uniquely identify a device.
    On Linux, Multipath is used to map a logical device name to a WWID - and using the same +/etc/multipath.conf+ configuration file on all cluster nodes, ensures that the same device names are used across the cluster.
    But from the the device file entry you listed, you're likely not running Linux? In that case, depending on the Unix flavour used and the type of cluster storage, there can be similar options to Linux's Multipath. One such option is EMC's PowerPath - but that of course is specific to EMC SANs and requires additional licensing fees.

  • ASM: cannot create asm disks - permission denied

    We cannot create ASM disks using the command:
    # /etc/init.d/oracleasm creatdisk ASMDISK1 /dev/mapper/mpathdp1
    Marking disk "ASMDISK1" as an ASM disk: [FAILED]
    The log (/var/log/oracleasm) has the following:
    Clearing disk header: done
    Disk "ASMDISK1" does not exist or is not instantiated
    Writing disk header: done
    Instantiating disk: oracleasm-instantiate-disk: Unable to create ASM disk "ASMDISK1": Permission denied
    failed
    Clearing disk header: done
    The command is being executed by the root user. Our environment is OEL6:
    [oracle@uxdbidbd1 mapper]$ uname -rm
    2.6.32-100.28.11.el6.x86_64 x86_64
    To install ASMLib we did the following:
    Installed the three packages:
    1.oracleasm-support-2.1.4-1.el5.x86_64.rpm
    2.oracleasmlib-2.0.4-1.el5.x86_64.rpm
    3.oracleasm-2.6.18-238.9.1.el5-debuginfo-2.0.5-1.el5.x86_64.rpm
    [root@uxdbidbd1 ~]# modprobe oracleasm
    [root@uxdbidbd1 ~]# /etc/init.d/oracleasm configure
    Configuring the Oracle ASM library driver.
    This will configure the on-boot properties of the Oracle ASM library
    driver. The following questions will determine whether the driver is
    loaded on boot and what permissions it will have. The current values
    will be shown in brackets ('[]'). Hitting <ENTER> without typing an
    answer will keep that current value. Ctrl-C will abort.
    Default user to own the driver interface []: oracle
    Default group to own the driver interface []: oinstall
    Start Oracle ASM library driver on boot (y/n) [n]: y
    Scan for Oracle ASM disks on boot (y/n) [y]: y
    Writing Oracle ASM library driver configuration: done
    Initializing the Oracle ASMLib driver: [  OK  ]
    Scanning the system for Oracle ASMLib disks: [  OK  ]
    [root@uxdbidbd1 ~]#
    [root@uxdbidbd1 ~]# /etc/init.d/oracleasm status
    Checking if ASM is loaded: yes
    Checking if /dev/oracleasm is mounted: yes
    Our SA partitioned the disk using fdisk:
    [root@uxdbidbd1 ~]# fdisk -l /dev/mapper/mpathd
    Disk /dev/mapper/mpathd: 52.4 GB, 52428800000 bytes
    255 heads, 63 sectors/track, 6374 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x4849251a
    Device Boot Start End Blocks Id System
    /dev/mapper/mpathdp1 1 6374 51199123+ 83 Linux
    Here are the owner/permissions:
    [oracle@uxdbidbd1 mapper]$ ls -al /dev/mapper/
    lrwxrwxrwx. 1 root root 7 Apr 22 14:58 mpathd -> ../dm-5
    brw-rw-r--. 1 oracle oinstall 253, 6 Apr 25 10:56 mpathdp1
    [oracle@uxdbidbd1 dev]$ ls -al /dev
    brw-rw----. 1 root disk 253, 5 Apr 22 15:45 dm-5
    drwxr-xr-x. 4 root root 0 Apr 22 14:58 oracleasm
    [oracle@uxdbidbd1 oracleasm]$ ls -al /dev/oracleasm
    total 0
    drwxr-xr-x. 4 root root 0 Apr 22 14:58 .
    drwxr-xr-x. 23 root root 7200 Apr 24 03:41 ..
    -rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .check_iid
    drwxr-xr-x. 1 root root 0 Apr 22 14:58 disks
    -rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .get_iid
    drwxrwx---. 1 oracle oinstall 0 Apr 22 14:58 iid
    -rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .query_disk
    -rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .query_version
    We ran an strace on the createdisk command that is failing and I noticed this in the output file:
    28830 mknod("/dev/oracleasm/disks/ASMDISK1", S_IFBLK|0600, makedev(253, 6)) = -1 EACCES (Permission denied)
    28830 write(2, "oracleasm-instantiate-disk: ", 28) = 28
    28830 write(2, "Unable to create ASM disk \"ASMDI"..., 56) = 56
    We changed /dev/oracleasm/disks to 777 in order to test but we got the same result. Do we need to adjust the permissions to all of the parent directories in the path (/dev/oracleasm/disks)? I've been looking around for anything related to permissions on /dev/oracleasm but the docs don't mention anything. Any help would be greatly appreciated.

    From what I understand, you should not set device permissions of /dev/oracleasm since oracleasm takes care of it according to /etc/init.d/oracleasm configure.
    The problem in your case seems to be that ASM refuses to initialize and write metadata to your device. Was the device previously used by ASM? ASM will fail to initialize a device that contains previous ASM metadata. To erase the device you will need to use the dd command, e.g. dd if=/dev/zero of=/dev/sdb. Both ASMLib and raw devices require the candidate disks to be partitioned before they can be accessed. To create a partition on /dev/sdb, for instance, type fdisk /dev/sdb and create a standard partition using the defaults. This will create /dev/sdb1 and you can try oracleasm createdisk again.
    You may try the above, but anyway, I was not sure how much you can trust your installation. The problem could also be that you installed the oracleasm kernel driver and asmlib software for OEL 5. Oracle Linux 6 includes an oracleasm kernel driver and as far as I remember you must not install another oracleasm kernel driver. Using modprob oracleasm and installing oracleasm support package using yum should do the trick. You may also need to download and install the asmlib package for the Oracle ASM grid install to see the ASM disks.

  • Empty ASM disk group [INS-30507]

    Hello Good people!
    I have SUSE Linux Enterprise Server 11 (x86_64) and grid infrastucture 11.2.
    I have installed ASMlib, and made
    /etc/init.d/oracleasm status
    Checking if ASM is loaded: yes
    Checking if /dev/oracleasm is mounted: yes
    /etc/init.d/oracleasm querydisk ASMDISK1
    Disk "ASMDISK1" is a valid ASM disk
    Then i am trying install grid infrastucture, on step CONFIGURE ORACLE GRID nfrastucture for Standalone Server,
    i can`t find my Disk "ASMDISK1"
    Why grid infrastucture can`t find my Disk "ASMDISK1"?

    ssolbach,
    i am trying to deletedisk ASMDISK1 using root.
    etc/init.d/oracleasm configure
    Configuring the Oracle ASM library driver.
    Default user to own the driver interface [oracle]:
    Default group to own the driver interface [oinstall]:
    Start Oracle ASM library driver on boot (y/n) [y]:
    Scan for Oracle ASM disks on boot (y/n) [y]:
    Writing Oracle ASM library driver configuration: done
    Initializing the Oracle ASMLib driver: done
    Scanning the system for Oracle ASMLib disks: done
    /etc/init.d/oracleasm status
    Checking if ASM is loaded: yes
    Checking if /dev/oracleasm is mounted: yes
    *******************************************************************

  • ASM Disk creation failed

    Dear Team,
                             I am using OEL 6.0 32 bit in Virtual Machine.I have installed all ASMlib rpm whatever required & SELINUX also DISABLE.But when I am trying to create ASM disk its giving below error.Please help me How can overcome this issue.
    [root@rac1 ~]# oracleasm createdisk ASM01 /dev/sdb1
    Writing disk header: done
    Instantiating disk: failed
    Clearing disk header: done
    [root@rac1 ~]#
    Regards,
    Praveen

    Did you configure the ASM lib ?
    /etc/init.d/oracleasm configure
    [root@node2 ~]# /etc/init.d/oracleasm configure
    Configuring the Oracle ASM library driver.
    This will configure the on-boot properties of the Oracle ASM library
    driver.  The following questions will determine whether the driver is
    loaded on boot and what permissions it will have.  The current values
    will be shown in brackets ('[]').  Hitting <ENTER> without typing an
    answer will keep that current value.  Ctrl-C will abort.
    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  ]
    [root@node2 ~]# /usr/sbin/oracleasm createdisk DISK101 /dev/sdc1
    Writing disk header: done
    Instantiating disk: done

  • How to rename voting disk name in oracle clusterware 11gr2

    Hi:
    I need change the name of voting disk at os level, original name is /dev/rhdisk20, I need rename to /dev/asmocr_vote1 (unix AIX), the voting disk is locate in ASM diskgroup +OCR.
    Initial voting disk was: /dev/rhdisk20 in diskgroup +OCR
    #(root) /oracle/GRID/11203/bin->./crsctl query css votedisk
    ## STATE File Universal Id File Name Disk group
    1. ONLINE a2e6bb7e57044fcabf0d97f40357da18 (/dev/rhdisk20) [OCR]
    I createt a new alias disk name:
    #mknod /dev/asmocr_vote01 c 18 10
    # /dev->ls -lrt|grep "18, 10"
    brw------- 1 root system 18, 10 Aug 27 13:15 hdisk20
    crw-rw---- 1 oracle asmadmin 18, 10 Sep 6 16:57 rhdisk20 --> Old name
    crw-rw---- 1 oracle asmadmin 18, 10 Sep 6 16:59 asmocr_vote01 ---> alias to old name, the new name.
    After change votingn disk unix name, the cluster doesn't start, voting disk is not found by CRSSD.
    -STEPS to start clusterware after changing the OS voting disk name are:
    1- stop al nodes:
    #crsctl stop crs -f (every node)
    Work only in one node (node1, +ASM1 instance):
    2- Change asm_diskstring in init+ASM1.ora:
    asm_diskstring = /dev/asm*
    3- change disk unix permiss:
    # /dev->ls -lrt|grep "18, 10"
    brw------- 1 root system 18, 10 Aug 27 13:15 hdisk20
    crw-rw---- 1 root system 18, 10 Sep 6 16:59 asmocr_vote01
    crw-rw---- 1 oracle asmadmin 18, 10 Sep 6 17:37 rhdisk20
    #(root) /dev->chown oracle:asmadmin asmocr_vote01
    #(root) /dev->chown root:system rhdisk20
    #(root) /dev->ls -lrt|grep "18, 10"
    brw------- 1 root system 18, 10 Aug 27 13:15 hdisk20
    crw-rw---- 1 oracle asmadmin 18, 10 Sep 6 16:59 asmocr_vote01 --> new name only have oracle:oinstall
    crw-rw---- 1 root system 18, 10 Sep 6 17:37 rhdisk20
    4-start node in exclusive mode:
    # (root) /oracle/GRID/11203/bin->./crsctl start crs -excl
    CRS-4123: Oracle High Availability Services has been started.
    CRS-2672: Attempting to start 'ora.mdnsd' on 'orarac3intg'
    CRS-2676: Start of 'ora.mdnsd' on 'orarac3intg' succeeded
    CRS-2672: Attempting to start 'ora.gpnpd' on 'orarac3intg'
    CRS-2676: Start of 'ora.gpnpd' on 'orarac3intg' succeeded
    CRS-2672: Attempting to start 'ora.cssdmonitor' on 'orarac3intg'
    CRS-2672: Attempting to start 'ora.gipcd' on 'orarac3intg'
    CRS-2676: Start of 'ora.cssdmonitor' on 'orarac3intg' succeeded
    CRS-2676: Start of 'ora.gipcd' on 'orarac3intg' succeeded
    CRS-2672: Attempting to start 'ora.cssd' on 'orarac3intg'
    CRS-2672: Attempting to start 'ora.diskmon' on 'orarac3intg'
    CRS-2676: Start of 'ora.diskmon' on 'orarac3intg' succeeded
    CRS-2676: Start of 'ora.cssd' on 'orarac3intg' succeeded
    CRS-2672: Attempting to start 'ora.ctssd' on 'orarac3intg'
    CRS-2672: Attempting to start 'ora.drivers.acfs' on 'orarac3intg'
    CRS-2679: Attempting to clean 'ora.cluster_interconnect.haip' on 'orarac3intg'
    CRS-2681: Clean of 'ora.cluster_interconnect.haip' on 'orarac3intg' succeeded
    CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'orarac3intg'
    CRS-2676: Start of 'ora.ctssd' on 'orarac3intg' succeeded
    CRS-2676: Start of 'ora.drivers.acfs' on 'orarac3intg' succeeded
    CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'orarac3intg' succeeded
    CRS-2672: Attempting to start 'ora.asm' on 'orarac3intg'
    CRS-2676: Start of 'ora.asm' on 'orarac3intg' succeeded
    CRS-2672: Attempting to start 'ora.crsd' on 'orarac3intg'
    CRS-2676: Start of 'ora.crsd' on 'orarac3intg' succeeded
    5-check votedisk:
    # (root) /oracle/GRID/11203/bin->./crsctl query css votedisk
    Located 0 voting disk(s).
    --> NO VOTING DISK found
    6- mount diskgroup of voting disk (+OCR in this case) in +ASM1 instance:
    SQL> ALTER DISKGROUP OCR mount;
    7-add votedisk belongs diskgroup +OCR:
    # (root) /oracle/GRID/11203/bin->./crsctl replace votedisk +OCR
    Successful addition of voting disk 86d8b12b1c294f5ebfa66f7f482f41ec.
    Successfully replaced voting disk group with +OCR.
    CRS-4266: Voting file(s) successfully replaced
    #(root) /oracle/GRID/11203/bin->./crsctl query css votedisk
    ## STATE File Universal Id File Name Disk group
    1. ONLINE 86d8b12b1c294f5ebfa66f7f482f41ec (/dev/asmocr_vote01) [OCR]
    Located 1 voting disk(s).
    8-stop node:
    #(root) /oracle/GRID/11203/bin->./crsctl stop crs –f
    8-start node:
    #(root) /oracle/GRID/11203/bin->./crsctl start crs
    10- check:
    # (root) /oracle/GRID/11203/bin->./crsctl query css votedisk
    ## STATE File Universal Id File Name Disk group
    1. ONLINE 86d8b12b1c294f5ebfa66f7f482f41ec (/dev/asmocr_vote01) [OCR]
    Vicente.
    HP.
    Edited by: 957649 on 07-sep-2012 13:11

    There is no facilty to rename a column name in Oracle 8i. This is possible from Oracle 9.2 version onwards.
    For you task one example given below.
    Example:-
    Already existed table is ITEMS
    columns in ITEMS are ITID, ITEMNAME.
    But instead of ITID I want ITEMID.
    Solution:-
    step 1 :- create table items_dup
    as select itid itemid, itemname from items;
    step 2 :- drop table items;
    step 3 :- rename items_dup to items;
    Result:-
    ITEMS table contains columns ITEMID, ITEMNAME

Maybe you are looking for