ASM Disk Problem

My diskgroup have three disks.
The first disk state is NORMAL,
but secondly and thirdly disk state is FORCING,not to use it.
How to change disk'state ?

I encountered a similar problem in the past. If you look in the reference manual
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10755/dynviews_1018.htm#sthref2985, V$ASM_DISK.STATE=FORCING is described as
FORCING - Disk is being removed from the disk group without attempting to offload its data. The data will be recovered from redundant copies, where possible.
Have you tried rebalancing the diskgroup? Before issuing the statement below make sure you have backups. The rebalance does not implicate data loss, it will only uniformly redistribute the data. Nevertheless it always wise to have a backup before doing this on a production database.
alter diskgroup <diskgroup_name> rebalance;
If the rebalance works properly the second and third disks should automatically be dropped and you can re-add them to the diskgroup.
If this does not work for you, please file an itar with Oracle Support as you may need to apply the most recent patchset and other patches.

Similar Messages

  • Oracle 12c ASM Disk Problem on AIX

    Hi All,
    We need to install 12.1.0.2 DB with ASM option on AIX 7.1. When we start to install 12.1.0.2 grid installation, in the 3.step we could not show adding Candidate disks to ASM. Disks right are 660 and oracle:oinstall ownership.
    When we start to install 11gR2 installation on same platform we can see the Candidate Disk, and We can install 11gR2 ASM+DB on same platform. But for 12.1.0.2 is not.
    How can we add Candidate Disks to 12c ASM İnstallation for below step ? The disks which is not shown for this step are like below. After first error I have changed disks' ownership like oracle:asmadmin, it isn't solved. I need urgent help.

    Hi Sve,
    Thanks for replying me. What you have written are tried but not works. I have solved problem.
    The problem is related AIX platform. I have Solved problem with below steps.
    1- I have installed grid infrastructure with Software Only option.
    2- After install Software Only Standalone Grid, I have tried to install manually ASM instance. But I have taken this error. rtld: 0712-001 Symbol CreateIoCompletionPort was referenced and it is solved with this MOSC ID: Doc ID1949184.1)
    3- After Successfull 2.step you can now install ASM manually from asmca.

  • 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 ~]#

  • Problem creating asm disk groups after installation.

    I just completed the grid install successfully on Oracle Linux:
    Candidate ASM disks not showing up in 11.2 installer (Oracle Linux)
    Thanks for the help.
    I am running into the same type of issue where I can't see the asm disks like I ran ran into during the install.
    When I run asmca to create the addditional disk groups I don't see the two asmlib volumes.
    I tried changing the disk discovery path from the default and I still can't see the disks.
    $ /usr/sbin/oracleasm listdisks
    CRSVOL1
    DATAVOL1
    FRAVOL1
    Do the block devices need to be owned by grid?
    $ ls -l /dev/sdc
    brw-r----- 1 root disk 8, 32 Aug 2 15:21 /dev/sdc
    $ ls -l /dev/sdd
    brw-r----- 1 root disk 8, 48 Aug 2 15:21 /dev/sdd
    $ ls -l /dev/sde
    brw-r----- 1 root disk 8, 64 Aug 2 15:21 /dev/sde
    How can the installer work fine and see the disks and then asmca can't see the disks?
    It must be a permissions issue. How can I see what the error is that is preventing the disks from showing up?

    $ cd /dev/oracleasm
    node 2:
    $ cd /dev/oracleasm
    $ ls -lL
    total 0
    -rw-rw---- 1 grid asmadmin 0 Aug 15 11:08 .check_iid
    drwxr-xr-x 1 root root 0 Aug 15 11:08 disks/
    -rw-rw---- 1 grid asmadmin 0 Aug 15 11:08 .get_iid
    drwxrwx--- 1 grid asmadmin 0 Aug 15 11:08 iid/
    -rw-rw---- 1 grid asmadmin 0 Aug 15 11:08 .query_disk
    -rw-rw---- 1 grid asmadmin 0 Aug 15 11:08 .query_version
    $ ls -lL disks/*
    brw-rw---- 1 grid asmadmin 8, 33 Aug 15 11:08 disks/CRSVOL1
    brw-rw---- 1 grid asmadmin 8, 49 Aug 15 11:08 disks/DATAVOL1
    brw-rw---- 1 grid asmadmin 8, 65 Aug 15 11:08 disks/FRAVOL1
    node 1:
    $ cd /dev/oracleasm
    $ ls -lL
    total 0
    -rw-rw---- 1 grid asmadmin 0 Aug 15 12:30 .check_iid
    drwxr-xr-x 1 root root 0 Aug 15 12:30 disks/
    -rw-rw---- 1 grid asmadmin 0 Aug 15 12:30 .get_iid
    drwxrwx--- 1 grid asmadmin 0 Aug 15 12:30 iid/
    -rw-rw---- 1 grid asmadmin 0 Aug 15 12:30 .query_disk
    -rw-rw---- 1 grid asmadmin 0 Aug 15 12:30 .query_version
    $ ls -lL disks/*
    brw-rw---- 1 grid asmadmin 8, 33 Aug 15 12:30 disks/CRSVOL1
    brw-rw---- 1 grid asmadmin 8, 49 Aug 15 12:30 disks/DATAVOL1
    brw-rw---- 1 grid asmadmin 8, 65 Aug 15 12:30 disks/FRAVOL1

  • Installing Oracle 11gR2 RAC Problem: ASM disks

    Folks,
    Hello. I am installing Oracle 11gR2 RAC using 2 Virtual Machines (rac1 and rac2 whose OS are Oracle Linux 5.6) in VMPlayer and according to the tutorial
    http://appsdbaworkshop.blogspot.com/2011/10/11gr2-rac-on-linux-56-using-vmware.html
    At the first time, I create VM rac1. While its OS Oracle Linux 5.6 is booting, initializing ASMLib Driver OK. I create 5 ASM disks successfully using the command:
    [root@rac1 /]# /etc/init.d/oracleasm createdisk ASMDISK1 /dev/sdb1
    Output: Marking disk "ASMDISK1" as an ASM disk: OK
    Because the hard disk space of rac1 is not enough to install Database, I create VM rac1 again with bigger hard disk space (30GB). I do everything the same with that at the first time. But this time, While OS Oracle Linux 5.6 is booting, initializing ASMLib Driver failed. I create 5 ASM disks using the same command:
    [root@rac1 /]# /etc/init.d/oracleasm createdisk ASMDISK1 /dev/sdb1
    Output: Marking disk "ASMDISK1" as an ASM disk: failed
    But when I use the command:
    [root@rac1 /]# /etc/init.d/oracleasm listdisks
    Output: ASMDISK1 ASMDISK2 ASMDISK3 ASMDISK4 ASMDISK5
    My questions are:
    First, can the 5 disks "ASMDISK1 ASMDISK2 ASMDISK3 ASMDISK4 ASMDISK5" be used correctly in spite of Marking disk "ASMDISK1(2 3 4 5)" as an ASM disk failed ?
    Second, how to fix OS Oracle Linux 5.6 so that initializing ASMLib Driver OK while booting ?
    Thanks.

    Folks,
    Hello. The issue is solved by myself. Thanks.

  • Reinstalling Oracle 11gR2 RAC Grid Problem - ASM Disks Group

    Folks,
    Hello.
    I am installing Oracle 11gR2 RAC using 2 Virtual Machines (rac1 and rac2 whose OS are Oracle Linux 5.6) in VMPlayer.
    I have been installing Grid Infrastructure using runInstaller in the first VM rac1 from step 1 to step 9 of 10.
    On the step 9 of 10 in the Wizard, accidentally, I touch the Mouse, and the Wizard is gone.
    The directory for installing Grid in the 2 VMs is the same: /u01
    In order to make sure everything is correct, I delete entire directory /u01 in the 2 VMs and install Grid in rac1 again.
    I have understood it's not the right way to delete /u01. The right way is to follow the tutorial
    http://docs.oracle.com/cd/E11882_01/install.112/e22489/rem_orcl.htm#CBHEFHAC
    But I have deleted /u01 and need to fix one by one. I install Grid again and get the error message on step 5 of 9 as follows:
    [INS - 30516] Please specify unique disk groups.
    [INS-3050] Empty ASM disk group.
    Cause - Installer has detected the disk group name provided already exists on the system.
    Action - Specify different disk group.
    In Wizard, the previous Disk Group name is "DATA" and its Candidate disks (5 ASMDISKs) are gone. I try to use a different name "DATA2", but no ASMDISKs come up under "Candidate disks". For "ALL Disks", all ASMDISKs cannot be selected.
    I want to use the same ASM disk group "DATA" and don't want to create a new disk group.
    My question is:
    How to have the previous ASM disks and its group "DATA" come up under "Candidate Disks" so that can use it again ?
    Thanks.

    Hi, in case this helps anyone else. I got this INS-30516 error too was stumped for little while. I have 2 x 2-node RAC which are hitting same SAN. The first-built RAC has a DATA diskgroup. When went to build second RAC on new ASM disk new DIskgroup (but same diskgroup name DATA) got INS-30516 about diskgroup name already in use etc. Finally figured out all that was required was to restrict diskstring using button in installer to only retrieve the LUNS for this RAC (this was quick and dirty - all LUNS for both RAC being presented to both RAC). Once diskstring only searched for the LUNS required for this RAC only, e.g.
    ORCL:DATA_P* (for DATA_PD and FRA_PD)
    the error went away.
    I also have DATA_DR and FRA_DR presenting to both RAC. Apparently it scans the header and if it finds a diskgroup name that is already in use based on the diskstring scan it will not allow reuse of the diskgroup name since it has no way of knowing that the other ASM disks are for a different RAC.
    HTH

  • Asm disk removed taking too much time to boot

    hi
    a local machine is configured with ASM by oracleasm with a total disk.As it was a training purpose so i have removed the disk eg /dev/sdb bluntly ie. just removing it from box.now i tried fsck -c -c -f /dev/ in rescue mode its didnot worked even not mounting the /mnt/sysimage.It claims for ext2fs error and mounting the fs etc.
    Then after lots of days has gone.i fed up with this issues and reinstalled OS.
    but my question is what exactly to do?obviously re-installation is not the exact way to do.
    regards

    If the +/dev/sdb+ was an ASM disk, then it should not impact the o/s when it is removed. ASM instance itself will fail with an error saying something like it was not able to mount the disk group.
    If your system failed to boot correctly after this disk was removed, then +/dev/sdb+ contained more than just ASM data.
    We dynamically add and remove ASM (multipath'ed) disks via kpartx - while o/s is running. No reboot. No problems.
    I fail to see how a ASM disk could cause the type of problems you describe - unless it was more than just a disk used by ASM alone.

  • Questions on asm disk discovery:

    Questions on asm disk discovery:
    1)What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
    2)  Which one of the above two finally accounts for the disk discovery process?
    3)  We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we no long need to rely on the path to discover the asm disks, by setting asm_diskstring='ORCL:*' , ASM instance will identify the right disks automatically. However, I am not sure if setting asm_diskstring='ORCL:*' is the most economic way to do the discovery as I am not sure if Oracle will have to probe all the disks on the OS to determine the right disks. If Oracle has to screen all the disks in this way, then I think setting asm_diskstring='<path_to_asmlib_disk>' will be much faster, although this will be open to the persistent problem. Is my understanding correct?
    Thanks.

    From my understanding all disk you see in /dev/oracleasm/disks are the disks in your system that been discovered by asmlib at discovery stage.
    Currently, due to bug 13465545, ASM instance will discover disks from both locations, ASM_DISKSTRING and gpnp profile, which can cause some mess in disk representation for asm. You can check the settings using asmcmd command: dsget, and set to be the same using dsset.
    I think its more secure to set ASM_DISKSTRING to only the disks used by asm instance.
    ASMCMD> dsget
    Regards
    Ed

  • Questions on asm disk discover:

    Questions on asm disk discover:
    1)What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
    2) which one finally accounts for the disk discovery process?
    3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we do not rely on the path the discover the asmlib
    disks. asm_diskstring='ORCL:*' will identify the right disks. I am not sure if setting 'ORCL:*' is the most economic way as I am not sure if Oracle will have to scan all the disks
    on the OS and probe the disks that it has rigths to determine which disks belong to ASM. If Oracle has to screen all the disks in this way, then I think setting
    asm_diskstring='<path_to_asmlib_disk>' will be much faster. However, this will be open to the persistent problem. Is my understanding correct?
    Thanks.

    Questions on asm disk discovery:
    1)What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
    2)  Which one of the above two finally accounts for the disk discovery process?
    3)  We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we no long need to rely on the path to discover the asm disks, by setting asm_diskstring='ORCL:*' , ASM instance will identify the right disks automatically. However, I am not sure if setting asm_diskstring='ORCL:*' is the most economic way to do the discovery as I am not sure if Oracle will have to probe all the disks on the OS to determine the right disks. If Oracle has to screen all the disks in this way, then I think setting asm_diskstring='<path_to_asmlib_disk>' will be much faster, although this will be open to the persistent problem. Is my understanding correct?
    Thanks.

  • 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

  • Correct steps to reload ASM disks into a running ASM instance on Linux RHEL

    Hi guys,
    i hope this is the correct forum, awfully i did not found any document specifically talking abou this.
    first of all let me explain quickly my goal: in my server (it contains the same data of 3 production RACs for reporting purposes) i would like to shutdown a single instance (i have 3) and realod his disks to refresh the data or because for some reason its mount into ASM is failed.
    this is a mix of Oracle ASM and Linux stuff...
    on this server there is a shell script that perform the following steps:
    1) shutdown 3 instances of 11g (11.2.0.2.0 with patch for asm already installed for bug... dont remember)
    2) shutdown ASM instance
    3) stop ASMLIB
    4) stop multipathd
    5) remove all disks devices from linux
    6) take a snapshot on the 3 production RACs
    7) remap the disks to this server (SAN stuff)
    8) rescan the disks
    9) start ASMLIB
    10) start ASM instance
    11) mount the DiskGroups
    12) start 3 oracle instances
    this works fine... my problem is when i try to refresh the disks of just 1 of the 3 instances, i perform the following steps:
    1) stop instance ABC
    2) dismount ABC diskgroups related to ABC instance
    3) wait 5 seconds (dont ask... if idid it without ASM still have the disks locked)
    4) delete the ASMLIB disks (oracleasm deletedisk XYZ) relate to such diskgroups
    5) remove mpaths related to the disks that need to be refreshed or correctly mounted oneagain
    6) remove devices
    7) unmap disks on SAN
    8) take snapshot (clone disks)
    9) map disks from SAN
    10) delete bindings file
    11) rescan devices
    12) execute multipath command (to rebuild bindings file)
    13) execute oracleasm scandisks
    14) mount DiskGroups
    15) start instance ABC
    actually i dont understand why the OS (or specifically ASMLIB) do not recognize me anymore one of the ASMLIB disk
    do you have any idea ? or im completly crazy doing that ?
    best regards,
    Luca

    Hi,
    well this step
    4) delete the ASMLIB disks (oracleasm deletedisk XYZ) relate to such diskgroups
    is not good. Because it will clear the ASM Header and as a result ASM will never again be able to detect the disks.
    So it is clear that "scnadisks" later will not see the disks, because you wiped them.
    Worse: You did the snapshot after deleting them... this gets tricky to get them "repaired" again.
    However there is the possibility to relabel a dropped ASM disks. You need to open an SR for this, since the procedure to restore the lost ASM header is not that simple..
    Regards
    Sebastian

  • Why the ASM disks can't be used again?

    Platform: Suse9(2.6.5-7smp)Linux x86_64, Oracle10g(10.1.0.3) RAC with ASM on 8 nodes and 30TB raw disks.
    Problem:
    In the first time, we created a db with a ASM Disk Group named RAC_DATA. But because of some errors we decided uninstall them. The uninstallation steps included removing all db and asm instances, rac software and crs software by dbca and oui. And cleared the shared ocr.crs and vote.crs in device raw1 and raw2.
    In the second time, we installed the crs and rac successfully. But when we ran dbca to recreate a database, all asm disks are unavailable, they all still belongs to the RAC_DATA group . But we have deleted RAC_DATA group in the uninstallation. What's more, we removed all in $ORACLE_HOME, $ORACLE_BASE/admin and $ORACLE_CRS_HOME.
    I don't know where the information about asm disks group stored. How can I clear it completely and reuse these disks them again.

    The problem is the that ASM metadata still exists. You can use the dd command to clear the metadata from the ASM disks.
    dd if=/dev/zero of=/dev/raw/raw1 bs=8192 count=12800
    Substitute the name of your device for /dev/raw/raw1 above. For further information see metalink note 26848.1 Re-Creating ASM instances and Diskgroups.

  • INS-30508 Invalid ASM disks on 11.2.0.3 OL 6.2 grid standalone install

    New set of Dell servers R710s running OL 6.2 redhat compatible kernel
    $ uname -a
    Linux seoltpo-02 2.6.32-220.el6.x86_64
    Connected to EMC VNX5500 and using powerpath 5.6.0. Not a rac environment ... doing 11.2.0.3 base install of grid infrastructure for a standalone server.
    Not using ASMLIB.
    Disk permissions are correct as grid install begins ...
    brw-rw---- 1 grid oinstall 120, 704 Jul 26 21:18 emcpoweras
    brw-rw---- 1 grid oinstall 120, 720 Jul 26 21:18 emcpowerat
    brw-rw---- 1 grid oinstall 120, 736 Jul 26 21:18 emcpowerau
    brw-rw---- 1 grid oinstall 120, 752 Jul 26 21:18 emcpowerav
    brw-rw---- 1 grid oinstall 120, 768 Jul 26 21:18 emcpoweraw
    brw-rw---- 1 grid oinstall 120, 784 Jul 26 21:18 emcpowerax
    brw-rw---- 1 grid oinstall 120, 800 Jul 26 21:18 emcpoweray
    brw-rw---- 1 grid oinstall 120, 816 Jul 26 21:18 emcpoweraz
    GUI installer sees the powerpath LUNs after changing the Disk Discovery path ... for example ....
    INFO: ... discoveryString = /dev/emcpower*
    INFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpower*']
    with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() {  eval `/usr/bin/modulecmd bash $*`
    }, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
    INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
    INFO: Parsing 40960 CANDIDATE /dev/emcpoweras grid oinstall
    INFO: Parsing 40960 CANDIDATE /dev/emcpowerat grid oinstall
    INFO: Parsing 40960 CANDIDATE /dev/emcpowerau grid oinstall
    INFO: Parsing 40960 CANDIDATE /dev/emcpowerav grid oinstall
    INFO: Parsing 40960 CANDIDATE /dev/emcpoweraw grid oinstall
    INFO: Parsing 40960 CANDIDATE /dev/emcpowerax grid oinstall
    INFO: Parsing 40960 CANDIDATE /dev/emcpoweray grid oinstall
    INFO: Parsing 40960 CANDIDATE /dev/emcpoweraz grid oinstall
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweru
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweru"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    *** Of course there are other LUNs not going to be part of ASM disk groups so it cannot read all of them initially.
    Somehow after first looking at the disks and seeing them the first time the permissions are changed back on the disks over to root:root as soon as the GUI sees the disks.
    You select the disks that you want in the GUI ( but the permissions have been changed already ) so click Next and wham INS 30508 ...
    The Install log shows that kfod is apparently scanning the disks a bunch of time ... but before the error appears install log sees that permissions have changed.
    Somehow actions caused from running the GUI are changing the permissions? Something is wrong somewhere ... powerpath ? 11.2.0.3 on this kernel version ? Seems very bizarre ...
    NFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpoweras','/dev/emcpowerat','/dev/emcpowerau','/dev/emcpowerav','/dev/emcpoweraw','/dev/emcpowerax','/dev/emcpoweray','/dev/emcpoweraz']
    with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() {  eval `/usr/bin/modulecmd bash $*`
    }, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
    INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraz
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraz"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    INFO: The process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod exited with code 0
    INFO: Waiting for output processor threads to exit.
    INFO: Parsing Additional information: 12247695
    INFO: Parsing Additional information: 1598903119
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweray
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweray"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    INFO: Parsing Additional information: 12247695
    INFO: Parsing Additional information: 1598903119
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerax
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerax"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    INFO: Parsing Additional information: 12247695
    INFO: Parsing Additional information: 1598903119
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraw
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraw"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    INFO: Parsing Additional information: 12247695
    INFO: Parsing Additional information: 1598903119
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerav
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerav"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    INFO: Parsing Additional information: 12247695
    INFO: Parsing Additional information: 1598903119
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerau
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerau"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    INFO: Parsing Additional information: 12247695
    INFO: Parsing Additional information: 1598903119
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerat
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerat"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    INFO: Parsing Additional information: 12247695
    INFO: Parsing Additional information: 1598903119
    INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweras
    INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweras"
    INFO: Parsing Linux-x86_64 Error: 13: Permission denied
    INFO: Parsing Additional information: 42
    INFO: Parsing Additional information: 12247695
    INFO: Parsing Additional information: 1598903119
    INFO: Output processor threads exited.
    SEVERE: [FATAL] [INS-30508] Invalid ASM disks.
    CAUSE: The disks [dev/emcpoweras, /dev/emcpowerat, /dev/emcpowerau, /dev/emcpowerav, /dev/emcpoweraw, /dev/emcpowerax, /dev/emcpoweray, /dev/emcpoweraz] were not valid.
    ACTION: Please choose or enter valid ASM disks.
    INFO: Advice is ABORT
    INFO: Adding ExitStatus INVALID_USER_INPUT to the exit status set
    INFO: Completed validating state <CreateASMDiskGroup>
    INFO: Terminating all background operations
    INFO: Terminated all background operations
    INFO: Transition aborted
    INFO: Rolled back to state <CreateASMDiskGroup>
    Is there some kind of configuration steps I am missing somewhere?
    Yeah I know probably going to have to open an SR here but some of you guys around here are pretty sharp. Can I attach the whole install log here somehow?

    Well I am not exactly opposed to udev rules for the powerpath devices ... not that I know what that is exactly ... if this can fix my problem.
    I found an example or two from google ...
    It looks like on my OL 6.2 system there is a difference in the files ( rules I guess ) under /etc/udev/rules.d
    # *** OL 5.7 system below
    $ ls -ltr
    total 232
    -rw-r--r-- 1 root root 1088 Jun 6 2007 60-pcmcia.rules
    -rw-r--r-- 1 root root 58016 Jun 6 2007 60-libsane.rules
    -rw-r--r-- 1 root root 2319 Jul 14 2008 bluetooth.rules
    -rw-r--r-- 1 root root 114 Nov 5 2008 90-alsa.rules
    -rw-r--r-- 1 root root 1823 Nov 5 2008 85-pcscd_ccid.rules
    -rw-r--r-- 1 root root 316 Dec 8 2010 60-raw.rules
    -rw-r--r-- 1 root root 82 Jan 13 2011 90-hal.rules
    -rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
    -rw-r--r-- 1 root root 292 May 11 2011 98-kexec.rules
    -rw-r--r-- 1 root root 143 Jun 7 2011 60-net.rules
    -rw-r--r-- 1 root root 331 Jun 9 2011 90-ib.rules
    -rw-r--r-- 1 root root 992 Jul 8 2011 40-multipath.rules
    -rw-r--r-- 1 root root 9366 Jul 22 2011 60-wacom.rules
    -rw-r--r-- 1 root root 107 Jul 22 2011 95-pam-console.rules
    -rw-r--r-- 1 root root 61 Jul 22 2011 90-dm.rules
    -rw-r--r-- 1 root root 471 Jul 22 2011 51-hotplug.rules
    -rw-r--r-- 1 root root 16732 Jul 22 2011 50-udev.rules
    -rw-r--r-- 1 root root 515 Jul 22 2011 05-udev-early.rules
    -rw-r--r-- 1 root root 175 Jul 22 2011 88-clock.rules
    # *** OL 6.2 system below
    $ ls -ltr
    total 64
    # *** OL 6.2 system below
    $ ls -ltr
    total 64
    -rw-r--r--. 1 root root 1914 Apr 27 2010 85-pcscd_ccid.rules
    -rw-r--r--. 1 root root 320 Jul 2 2010 90-alsa.rules
    -rw-r--r--. 1 root root 1060 Jul 24 2010 60-pcmcia.rules
    -rw-r--r--. 1 root root 1652 Nov 20 2010 60-fprint-autosuspend.rules
    -rw-r--r--. 1 root root 2486 Dec 23 2010 97-bluetooth-serial.rules
    -rw-r--r-- 1 root root 935 Mar 7 2011 95-dataeng-udev.rules
    -rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
    -rw-r--r--. 1 root root 706 Mar 29 2011 56-hpmud_support.rules
    -rw-r--r--. 1 root root 6858 Mar 29 2011 40-hplip.rules
    -rw-r--r--. 1 root root 83 May 20 2011 90-hal.rules
    -rw-r--r--. 1 root root 316 Oct 13 2011 60-raw.rules
    -rw-r--r--. 1 root root 54 Dec 7 2011 99-fuse.rules
    -rw-r--r--. 1 root root 292 Dec 7 2011 98-kexec.rules
    -rw-r--r--. 1 root root 53 Dec 7 2011 91-drm-modeset.rules
    -rw-r--r--. 1 root root 789 Jul 19 07:28 70-persistent-cd.rules
    ??? So no file 50-udev.rules ... in the 6.2 system ??? But tons of stuff in the 5.7 system ...

  • Oracleasm cannot find asm disks on boot

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

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

  • Using udev devices for ASM disk on Linux

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

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

Maybe you are looking for

  • How do I recover bookmarks and passwords after an O/S change, and the old programs are in a windows.old folder?

    Recently, I had a non-recoverable crash of my Windows XP Pro system. I clean-installed Vista (would not allow an upgrade install), and it moved all of my settings and programs into a windows.old folder. I'd like to be able to recover my stored passwo

  • Table For Production Order as per MD04

    Hi,   I making a report in which i want to take all the open production order as per MD04 transacton,  in MD04  when we check the material if there is any open production we can see in MD04,  i want to read all those orders from a table  i have in AF

  • Top n Analysis using correlated subquery

    Please explain this query. It is doing top n analysis using correlated subquery. I need explaination of execution of this query. Select distinct a.sal From emp a where 1=(select count ( distinct b.sal) from emp b      where a.sal <=b.sal) Thanks in a

  • Oracle Security Patch Error while applying --The filename, directory name,

    Hello, I am running into strange error while applying Oracle Security Patch 68 by using Opatch. Supposedly, All the environment variables are set properly. ACTIVE_STATE_PERL=true DBMS_TYPE=ORA dbs_ora_tnsname=YBQ JAVA_HOME=C:\jdk1.3.1_10 OPATCH_DEBUG

  • SAPehpi and Windows distributed environment

    Hi,  We have Windows platform with Oracle databases in distributed and high-availability environment. I have tried to install EHP1 for PI 7.1.  I have used SAPehpi as described in installation manual.  SAPehpi will stop when querying database informa