ASM disk discovery

Hi
I am trying to use ASM in my windows server (xp). my database version is 10.2.0.3.
1. I have add disk by asmtool as under
a. j:\ partition of my windows I dropped then recreate the partition without file system with drive letter j:
b. C:\>asmtool -add -force j:
2. From DBCA I choice option ASM configure . ASM instance created but I am not able to discover the disk so not able to create disk group
please guide me in this regards
Rabi
Edited by: user623166 on Jul 11, 2011 4:57 AM

I think you have to check whether you have given the permissions for the ORACLE user on the disk which you supposed to create the diskgroup ..If you have given the permission then check whether that disk is formatted with any filesystem..Make sure that disk must not be formatted. if the disk is not yet formatted then please check whether its displaying the disks on the OS...GoodLuck!

Similar Messages

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

  • What is ORCL prefix for in ASM Disks?

    version: 11.2 / RHEL 5.8
    Once the ASM Disk is created using oracleasm, you can add the ASM Disk to the disk group like
    SQL> alter diskgroup DATA1 add disk 'ORCL:DISK2';
    Diskgroup altered.Is the prefix "ORCL:" mandatory ? What is it for, anyway ?

    Oh ok. This means ASM Disks discovery path is hard coded to ORCL.
    This is why ASM_DISKSTRING is not set for ASM instances using ASMlib (as shown below). Right ?
    SQL> show parameter asm_diskstring
    NAME                                 TYPE        VALUE
    asm_diskstring                       string

  • ASM disks are not found at node2 on vmware

    Hi All,
    I'm very new to Oracle RAC. I was tring to install 10g rac in my desktop using vmware workstation. Also I configured the shared storage. Here i'hv rac1 and rac2 two virtual machines. while I created asm disks (ASM1,ASM2,ASM3) on rac1. While listing the asm disks at rac1 display the correct result but rac2 not returning anything.
    Can anybody suggest on this. B'coz I tried several times rac installation and but it failed bcoz of mismatch ocr id.
    Thanks

    Does rac2's operating system see the disks? Assuming Linux for the remainder of this post:
    Run "fdisk -l | more" on each node and compare the output. If you know the names of the devices (maybe something like: /dev/sdb /dev/sdc /dev/sdd), you can do an "ls -la /dev/sdb* " on each node and compare the file permissions and ownership. What is the ASM disk discovery string? Chances are rac2 has not picked up the new partitions created on rac1, which could be corrected by running "/sbin/partprobe /dev/sdb". If the device ownership is wrong, simply changing it as the root user won't persist across reboots: you will need to setup udev rules to re-apply permissions and ownership for each boot.
    Only when the operating system device files are present, and owned by the correct user ("grid" or "oracle", depending on your installation), then you will be able to scan for the devices in ASM. In the case of RAC, you'll also need to ensure the device files are named identically between nodes. ASMLIB can help, but something like device mapper (/etc/multipath.conf, can be configured even to manage a single path as is the case when using a vmware's vmdk virtual disk) is usually a more robust solution in my opinion.
    Some folks incorrectly assume that ASM will eliminate the system administration tasks entirely. The only thing it eliminates is managing devices after they've been successfully configured for use by ASM. LUN creation, zoning, masking, OS provisioning to include HBA bindings et al, and lastly OS permissions are all still very much required.
    If still having problems, paste the above mentioned utility outputs and we will try to help you spot the issue.

  • ASM 11gR2 Disk Discovery

    Hi,
    I've got the following scenario:
    Say I have 3 ISCSI disks that is exposed to the 2 nodes as:
    /dev/disk1 --> say 10Gb
    /dev/disk2 --> say 20Gb
    /dev/disk3 --> say 30Gb
    I flag /dev/disk1 (the 10Gb disk) as a ASM disk and create a disk group.
    After the server reboot the order in which the discs are seen by the server change and they are exposed as:
    /dev/disk1 --> now the 30Gb
    /dev/disk2 --> now the 10Gb
    /dev/disk3 --> now the 20GB
    Will this be a problem for ASM?
    I'm sure I've read that ASM will automatically pickup the correct disk and mount the disk groups, but can't seem to find the document.
    Can anyone please point me to the documentation for this?
    Regards.

    I found the following at:
    http://www.oracle.com/technology/pub/articles/hunter-rac11gr2-iscsi.html#Create%20Partitions%20on%20iSCSI%20Volumes
    Create Persistent Local SCSI Device Names
    In this section, we will go through the steps to create persistent local SCSI device names for each of the iSCSI target names. This will be done using udev. Having a consistent local SCSI device name and which iSCSI target it maps to, helps to differentiate between the three volumes when configuring ASM. Although this is not a strict requirement since we will be using ASMLib 2.0 for all volumes, it provides a means of self-documentation to quickly identify the name and location of each iSCSI volume.
    So it don't look like it will be a problem.
    Can anybody maybe point me to the Oracle documentation stating this?
    Thanks in advance.

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

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

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

  • Creation of ASM disk for OUI

    I need to install a Oracle Database in order to install Enterprise Manager Cloud Control 12c.
    Need the database to use a ASM disk.
    I used the following command to create the disk, per the Oracle Database Installation Guide.
    #/usr/sbin/oracleasm createdisk DISK1 /dev/sdd1
    #oracleasm listdisks
    DISK1
    However, when running the OUI for Oracle Database 12c (understand 11.2.0.3 is certified for Cloud Control), step 7
    errors INS-30517 when attempting to select "Oracle Automatic Storage Management" for "Storage type".
    Researched the error at this location but no cause or action was provided.
    http://docs.oracle.com/cd/E16655_01/server.121/e26079/common_errormessages.htm
    INS-30517: Automatic Storage Management software is not configured on this system.
    The database install guide states that I need to ensure the "disk discovery string" is set the "ORCL:*" or is left empy ("") so the installer discovers these disks.
    It doesn't show how to confirm or change the settings.
    At this point I'm at a stopping point.

    All ASMLib installations require the oracleasmlib and oracleasm-support packages. The oracleasm kernel driver is included in the Oracle UEK kernel. Perhaps you are missing the oracleasmlib package. You can download it from:
    Oracle Linux: Oracle ASMLib | Oracle Technology Network
    Oracleasmlib is not necessary for ASM to work, but it contains software necessary for Linux oracleasm, including the /usr/sbin/oracleasm-discover utility, which the Oracle installer used in the previous 11g version to detect available ASM volumes.

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

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

  • Can't have ASM mark a NFS file as an ASM disk : -is not a block device

    Hello,
    I’m trying to experiment with ASM for learning purpose. Because I don’t have access to a SAN, I am trying to use NFS files but I can’t manage to have ASM mark those files as ASM disks.
    [root@localhost /]# /etc/init.d/oracleasm createdisk ASM_DISK_1 /mnt/asm_dsks/dg1/disk1
    Marking disk "ASM_DISK_1" as an ASM disk: [FAILED]
    The oracleasm log says: File "/mnt/asm_dsks/dg1/disk1" is not a block device
    OK, more context now:
    I am trying to install ASM on a RHEL5 virtual machine (on vmware).
    [root@localhost /]# uname -rm
    2.6.18-8.el5 x86_64
    I followed this document:
    http://www.oracle.com/technology/pub/articles/smiley-11gr1-install.html until I got stuck at the following command:
    /etc/init.d/oracleasm createdisk ...
    Now, the NFS filesystem comes from a Solaris 10 system (the only one that's available) running on a physical sun box (this one is not a virtual system).
    I have tried many combinations. I tried creating the files on the linux VM, using dd. As root, as oracle. I tried creating them on the Solaris side, using mkfile... no matter what I try, I always get the same issue.
    I tried to follow this document: Creating Files on a NAS Device for Use with ASM (http://download.oracle.com/docs/html/B10811_05/app_nas.htm#BCFHCIEC)
    But nothing seems to work.
    Any idea, recommendations?
    Thanks,
    Laurent.

    Hi buddy,
    I guess the metalink note 731775.1 should help You.
    In fact the procedure is:
    - Create the disk devices on your NFS directory (using dd)
    - Adjuste the permissions over those files (in this case, oracle:dba)
    - Adjust the ASM_DISKSTRING at the ASM instance and setting the NFS directory in the discovery path
    - Verify if they are available at v$asm_disk view
    - Create the diskgroup using the the NFS disks that You have created.
    Hope it helps,
    Cerreia

  • 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

  • Issue with ASM disk

    Hello,
    When using database configuration assistant to configure ASM and create disk group, it can't find any disk. I've tried to chage disk discovery path by using 'ORCL:*', '/dev/oracleasm/disk/*' and install procedure is as follow:
    TIA,
    Step 1 :
    # rpm -Uvh oracleasm-support-2.0.3-1.i386.rpm \
    oracleasm-2.6.9-42.0.0.0.1.ELsmp-2.0.3-2.i686.rpm \
    oracleasmlib-2.0.2-1.i386.rpm
    Step 2 :
    #vi /etc/sysconfig/rawdevices
    add a line
    /dev/raw/raw1 /dev/sdb1
    To bind the disk devices to the raw devices, enter the following command:
    # /sbin/service rawdevices restart

    Hi,
    Me also facing same issue while creating ASM.
    i done what you said,but now also i'm facing same issue. Please find below steps what i did.
    1) ]# /etc/init.d/oracleasm createdisk VOL1 /dev/sdb7
    Marking disk "VOL1" as an ASM disk: [FAILED]
    2) then i enter the raw devices in the below directory
    ]# vi /etc/sysconfig/rawdevices
    /dev/raw/raw7 /dev/sdb7
    3) then i changed the ownership root to oinstall
    4) then i given the permissions to the raw device
    5) after that i given the below command
    ]# dd if=/dev/zero of=/dev/raw/raw7 bs=1M count=100
    dd: opening `/dev/raw/raw7': Device or resource busy
    6) Then i tried the below way
    ]# dd if=/dev/zero of=/devsdb7 bs=1M count=100
    100+0 records in
    100+0 records out
    104857600 bytes (105 MB) copied, 0.077255 seconds, 1.4 GB/s
    7) then i tried to create the ASM Diskgroup but again i got same issue.
    Can you please give suggession to me it's very important to me
    Regards,
    Ram

  • ASM Disks not appearing

    I am installing Oracle RAC 10.2 on an EM64-T box, RedHat Linux 4, using a shared MSA1000 SAN for the shared storage.
    I have installed CSS (and it is running correctly), and have downloaded and installed the ASM libraries and Oracle.
    From the command line I can do an "oracleasm createdisk VOL1 /dev/sda2", then do a "listdisks" and see the device (VOL1) on BOTH nodes in my RAC cluster.
    Using DBCA, however, when I try to manage ASM it does not show the device (VOL1). I have confirmed that my Discovery path is ORCL:*.
    Any thoughts?

    hi,
    We face the same problem while setting up Oracle ASM on 10R2 RAC on RHEL4. you need to specify the disk path instead of string 'ORCL:'. specify string '/dev/oracleasm/disks/*' and then see, DBCA will show you all the ASM disks you have created.
    cheers
    Raj

  • ASM disk mappings

    Hi All
    With ASMlib when setting up ASM you add disks with a command such as this " /etc/init.d/oracleasm createdisk VOL1 /dev/sdg" as described in metalink article 275315.1. You can then query the disks ASMlib knows about using this command "/etc/init.d/oracleasm listdisks" or you can see the asm disk aliases again by querying "select disk_number, name, path, state from v$asm_disk;"
    My question is how do you see what the underlying alias maps to after the initial creation. Using the above example how do I see that "VOL1" maps to "/dev/sdg"
    Thanks
    Steve

    No I thought it should be to but that just gives the alias names again plus the ASM discovery string that it uses for the default location of the disks...I guess I need it to tell me what that resolves to.
    SQL> select path from v$asm_disk;
    PATH
    ORCL:DISK8
    ORCL:DISK10
    ORCL:DISK27
    ORCL:DISK26
    ORCL:DISK25
    ORCL:DISK23
    ORCL:DISK21
    ORCL:DISK19
    ORCL:DISK17
    ORCL:DISK15
    ORCL:DISK13
    ORCL:DISK11
    ORCL:DISK9
    ORCL:DISK7
    ORCL:DISK30
    ORCL:DISK29
    ORCL:DISK28
    ORCL:DISK24
    ...

Maybe you are looking for