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

Similar Messages

  • 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

  • How do you change your device name on the latest version of Itunes?

    I can't figure it out...

    Connect your device to iTunes. Select it in the device section (left) then click on its name (center of screen) and edit it. Or you do it on your device in Settings -> General -> About -> Name

  • 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

  • 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.

  • 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

  • Changing the Default name of DVD Disk in OneStep

    Is it possible to change the default name of the disk that is burned on iDVD 6 "OneStep DVD" ???
    the default disk name becomes "IDVDONESTEPDVD"...
    I make lots of DVD with OneStep and would like the name created to be different.
    Is this possible and if so...How??
    Thanks for your advice...
    STDigital

    Not sure if this is possible or not but did you already check the iDVD6 Help Menu and try the following?
    Choose Project > Project Info. Type the new name in the Disc Name box.
    If this approach isn't possible, then it's likely not a very good idea to change its default title. Good luck.
    (3) G4 PM's/(3) S-Drives/Sony TRV900/Nikons/6FWHD's/PS7/iLife06/FCPHD/DVDSP/etc. Mac OS X (10.4.8) My ichatav AIM account is: SDMacuser1 (Please use Text chat prior to video)

  • Is It  POSSIBLE to change the Technical Name of Z-version Query

    Hi  Friends ,
    I was changed all quereis and cube from standard version to Z version.
    For queries, by using rszc , i was changed to Zversion,Now again is it
    possible to change the Technical Name of Zversion Query ?
    If possible , can you please tell me the process ?

    Hi Hameed,
    This may be the reason you are getting an error.
    The target InfoCube, the InfoCube for the query copies, must contain all the InfoObjects of the source InfoCube (InfoCube of the original queries).
    The another reasons may be the copying of queries within the same cube shouldn't be done by RSZC.
    It's better to approach the Bex Query designer.
    Hope you understood..
    Check the link below for more information:
    Re: How to copy query elements without Bex
    http://www.bi-expertonline.com/article.cfm?session=&id=2055
    Re: copy queries + variants + workbooks -- RSZC ?
    Regards,
    Ravi Kanth
    Edited by: Ravi kanth on Jun 10, 2009 10:03 AM

  • HT201240 I have a new macbook pro that did not have a disk, OS X was pre installed  so how can i change the administrators name and password, it did not migrate properly from my hard drive.., so how do i

    I have a new macbook pro that did not have a disk, OS X lion 7.3.4 was pre installed  so how can i change the administrators name and password, it did not migrate properly from my hard drive.., now there is some mysterious administrator name and or password??

    See #5
    Step by Step to fix your Mac

  • System Disk Name Change - Restore Old Files?

    The name of a friend's main system disk was accidentally changed some time ago. The backup sets from both the old name and new name are still in TM under the same computer name. When we look at the backup sets they appears as (the leading dots are just to show the folder hierarchy since consecutive spaces are deleted):
    Backup.backupsdb
    ..computer_name
    ....2009-01-01-timecode
    ......Macintosh\ HD
    ....2009-06-01-timecode
    ......New\ Disk\ Name
    When we go in to TM to restore, we can see the backup sets that match the current disk name but not the ones with the old disk name.
    How can we go about restoring files that existed when the disk had the old name? Selecting "Browse Other TM Disks" does not show the backup sets with the old disk name.
    Any help is greatly appreciated.
    Ed

    OK, here is the whole story as I understand it (this is a friend's iMac).
    The drive was originally named "Machintosh HD". There are backup sets going back to August, 2008 where the only folder under the date folder in Backups.backupdb is named "Machintosh HD".
    In late August, 2008, the internal drive was renamed " `1| ". The only folder in the date folders in Backups.backupdb is named " `1| ".
    Two weeks ago we installed a new, larger internal HD. At that time, we discovered the problem with the drive name and renamed it "Machintosh HD". We are now able to restore from any backup where the folder in the date folders in Backups.backupdb is named "Machintosh HD".
    For the time period from late August, 2008 - August, 2009 TM greys out the dates for the backup sets. It will not allow us to restore from them.
    Prior to renaming the " `1| " drive, we could restore from any backup set between late August, 2008 - August 2009. We were not able to restore from the backup sets prior to August, 2008 where the name was "Machintosh HD".
    It appears that TM wants to see a directory that matches the internal drive name in order to allow a restore from it.
    I'm sorry for the confusion on the names. I have been using Unix systems for years and automatically include a \ when I type a file or directory name that includes a space.
    Ed

  • Harddrive (start up disk) name changed

    Why would the harddrive (start up disk) name change (on desktop) to an unrecognizable number/letter combination? Is it a virus?

    Extremely unlikely that you have any sort of malware causing this. (Malware affecting Macs does exist, but no known viruses do, & the rare, existing malware tries to be stealthy to avoid detection.)
    More likely: you accidentally changed the startup disk name somehow. Try changing it back & see what happens.
    Also, see the second item in the "More Like this" box to the right of this page for more info.
    Message was edited by: R C-R

  • NAS disk name changed - HELP!

    I use a NAS for backups and external storage.  At some time in the past week, my backup operations stopped working, and I think I have tracked down the source of the problem.  Somehow, an "extension" got added to the disk name (I did not do this and I am not sure how it happened).  The disk name (Cosmos) has not changed, but when right click and choose "get info", in the "Name and Extension" section, the disk shows up as Cosmos-1.  Unfortunately, the name is greyed out and I can't change it.  Does anybody know how I can remove the -1 extension and change the name back to Cosmos so that my backups see the disk again?  HELP!

    Open up Applications > Utilities > Terminal
    Type in
    cd /Volumes/
    ("Change Directory to /Volumes/")
    and then
    ls -a
    (list all the files in this directory)
    and you will probably see Cosmos and Cosmos-1, among others. Eject the Cosmos volume if you haven't already, then go back to Terminal. Type in
    rm Cosmos
    ("remove the file called Cosmos")
    Now mount the drive again and it should be able to take the name "Cosmos" without adding the '-1' suffix.
    These phantom volumes can sometimes appear when a command tries to copy files to a volume without actually mounting it first. It is likely that wahtever you are using to make backups isn't properly waiting for the drive to mount before it tries to do a backup.

  • 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

  • Migrating ASM disk from singlepath to multipath

    Hi,
    I need to migrate the single path for the SAN disks to a multipath access mode.
    Here is my environment :
    Oracle DB : 11gR2 Enterprise version (2 Node RAC)
    OS : Oracle Enterprise Linux 5
    DB file system : ASM disks with ASMLib
    disk used : SAN disk
    Multipath software : EMC Powerpath
    single path names are : /dev/sdb, /dev/sdc, .. etc.
    Multipath Name would be : /dev/emcpowera, /dev/emcpowerb etc.
    From different metalink document and google, I came up with the following steps for migrating the ASM disks from singlepath to multipath :
    (** Perform the below steps on both the nodes)
    1.     Open ASMLIB configuration file: /etc/sysconfig/oracleasm (Backup this file at this point)
    3.     Edit the variable ORACLEASM_SCANORDER to provide the prefix path of the multipath disk.
    For example:
    The multipath disk name would be /dev/emcpowera, /dev/emcpowerb etc. (Since we are using emc powerpath), set the ORACLEASM_SCANORDER variable as follows:
    ORACLEASM_SCANORDER="emcpower"
    4.     Edit the variable ORACLEASM_SCANEXCLUDE to exclude the single disks (/dev/sd*) from scan process.
    ORACLEASM_SCANEXCLUDE=”sd”
    5.     Reboot both the nodes.
    Are the above steps fine? Any addition/ modification needed ? Please advise.
    Raised an SR for this, but did not get a direct answer.
    Also. Do I need to set the ASM_DISKSTRING parameter to any specific value for my ASM instance? It is currently set to NULL.
    Thanks.

    Hi,
    no actually that's all there is to it.
    Since you use ASMLIB, the disks will be presented the same to ASM. So there is no need to change the DISCOVERY_STRING.
    Only thing I personally would do (for testing purposes) is the following:
    1.) Check before migrating that all disks are there (oracleasm listdisks), then
    2.) Disable the automatic startup of the crs stack (crsctl disable crs), that you can test everything (including reboot) without having the clustarstack start automatically.
    3.) If after the reboot the oracleasm listdisks sees all disks you are fine
    4.) Enable crs again (crsctl enable crs) and start the clusterstack (crsctl start crs).
    Regards
    Sebastian

  • 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.

Maybe you are looking for

  • Smartform to PDF and e_mail? Urgent

    hi all, i am able to convert smartform to pdf and download the pdf onto desktop but not able to send it as attachment thru email.  CALL FUNCTION 'CONVERT_OTF_2_PDF'            EXPORTING                 use_otf_mc_cmd         = 'X'            IMPORTIN

  • How can I make a "scaling scale" effect in photoshop? (soda can)

    Hey. As part of my production art class, I was making a soda can mockup from a tutorial. I thought of an effect that could make it look better, where I make the soda can label and water bubble layer larger than the can, then use a "scaling scale" tha

  • Perl 5.14

    I have  a rather simple problem. Two packages I need to use require different versions of perl. Squeezebox-Server is compiled to run with 5.12 max, munin requires 5.14. What is the suggested way to install and use both packages on one installation?

  • Texting

    why do some texts get sent as imessage and others as text message

  • Photoshop CS5 and Lightroom GUI

    Does anyone know about plans of redesign the Photoshop CS5 UI? In an older post Chris Cox said that it's on a feature request list. Can we take a look on that feature request list? Best regards R. Message was edited by: before&after