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

Similar Messages

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

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

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

  • Can not find disks when creating ASM disk group (11.0.2.3 on OEL 6)

    Hi
    I`m trying to install 11.0.2.3 Grid on OEL6.
    Every thing is fine until it prompt to ask where I want to put OCR and VOTING DISK. I choose to put them in ASM. So it prompt another window to ask create ASM DISK GROUP.
    In this window there was an area called "add disk". There suppose to be some disks listed in this area to chose. But in my case, nothing here. I can not chose disks to add to ASM DISK GROUP.
    Below are descriptions of my installation.
    Oracle Grid 11.0.2.3
    OEL 6 as the platform.
    I use two nodes mounting the same NFS. I created some zero-padded files on the NFS directory as the ASM DISKS. (This disks should be showing the the area above)
    I install everything using only one account oracle. The group is oinstall and dba
    Edited by: Kramer on Jun 5, 2013 8:52 PM

    Well as i see your asm_diskstring could be the problem. ASMlib would have been there isnt it , I would want you to stick to default value and then try also I would suggest you to once post the output of the following and lets see whats happening
    [root@ora ~]# /etc/init.d/oracleasm scandisks
    [root@ora ~]# /etc/init.d/oracleasm listdisks
    [root@ora ~]# ls -ltr /dev/oracleasm/disks/*

  • 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

  • Error while creating asm disk group

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

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

  • Cannot create ASM disk groups in DBCA - Oracle 11gR1, Windows 32bit

    Good afternoon,
    Using 11gR1 on Windows XP, I need help installing a database (single instance) using ASM, I am not able to select disks to be stamped for use by ASM. I have done the following steps:
    1. Installed the Oracle 11gR1 software (no database created - just the software)
    2. Connected nine (9) SCSI hard drives to the system
    3. Created a primary partition on each hard drive, formatted the partition but did *not* assign a drive letter
    4. Created a listener service (working properly - checked with lsnrctl  status)
    5. Started DBCA to create a single database instance using ASMIn DBCA I performed the following:
    a. at the welcome screen, click Next
    b. at "Step 1 of 16", click Next (accepting the default "Create a Database")
    c. at "Step 2 of 16", click Next (accepting the default "General Purpose or Transaction Processing)
    d. at "Step 3 of 16", "Global Database Name" set to "dbca", "SID" set to "dbca", click Next
    e. at "Step 4 of 16", click Next (accepting the defaults)
    f. at "Step 5 of 16", click "Use same administrative passwords for all accounts" and entered password, click Next
    g. at "Step 6 of 16", click "Automatic Storage Management (ASM)", click Next
    Everything seems just fine until I reach the following step
    h. at "Step 7 of 16", click "Create New"
        - The Create Disk Group window pops up (there is nothing shown in the "Select Member Disk Area")
        - set the "Disk Group Name" to  "DATAGROUP"
        - click on "Show All" (no devices shown after clicking)
        - click on "Stamp Disks..."  this causes the "asmtool operation" window to pop up
          - click on "Add or change label", click on Next
          - the "Select Disks" step appears.   There are 11 hard drives listed but NONE of them
            can be selected - all I can do here is click on Cancel*The question:* Why aren't the drives selectable and what do I need to do to make them selectable ?
    Thank you very much for your help,
    John.

    >
    The question: Why aren't the drives selectable and what do I need to do to make them selectable ?
    >
    To answer my own question (now that I've figured it out), the reason is because the partition should not be formatted.
    When Windows displays the "New Partition Wizard", it is important to:
    1. not assign a drive letter
    2. and select "Do not format this partition"
    This will cause Windows to mount the volume thus making it accessible to Oracle.
    Hopefully this will help someone not fall in this trap as I did,
    John.

  • Getting errors while creating asm disk groups

    while creating disk groups on 10gR2 database on linux redhat 5.3
    im getting following errors :
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15031: disk specification '/dev/raw/raw4' matches no disks
    ORA-15025: could not open disk '/dev/raw/raw4'
    ORA-27041: unable to open file
    Linux Error: 19: No such device
    Additional information: 42
    Additional information: 213402552
    Additional information: -1079643768
    ORA-15031: disk specification '/dev/raw/raw3' matches no disks
    ORA-15025: could not open disk '/dev/raw/raw3'
    ORA-27041: unable to open file
    Linux Error: 19: No such device
    Additional information: 42
    Additional information: 213402552
    Additional information: -1079643768
    ORA-15031: disk specification '/dev/raw/raw2' matches no disks
    ORA-15025: could not open disk '/dev/raw/raw2'
    ORA-27041: unable to open file
    Linux Error: 19: No such device
    Additional information: 42
    Additional information: 213402552
    Additional information: -1079643768
    ORA-15031: disk specification '/dev/raw/raw1' matches no disks
    ORA-15025: could not open disk '/dev/raw/raw1'
    ORA-27041: unable to open file
    Linux Error: 19: No such device

    these are contents of my initORCL.ora :
    ORCL.__db_cache_size=251658240
    ORCL.__java_pool_size=4194304
    ORCL.__large_pool_size=4194304
    ORCL.__shared_pool_size=104857600
    ORCL.__streams_pool_size=0
    *.audit_file_dest='/opt/oracle/product/10.2.0/db_1/admin/ORCL/adump'
    *.background_dump_dest='/opt/oracle/product/10.2.0/db_1/admin/ORCL/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='/opt/oracle/product/10.2.0/oradata/ORCL/control01.ctl','/opt/oracle/product/10.2.0/oradata/ORCL/control02.ctl','/opt/oracle/product/10.2.0/oradata/ORCL/control03.ctl'
    *.core_dump_dest='/opt/oracle/product/10.2.0/db_1/admin/ORCL/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='ORCL'
    *.db_recovery_file_dest='/opt/oracle/product/10.2.0/db_1/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=ORCLXDB)'
    *.job_queue_processes=10
    *.local_listener='LISTENER_ORCL'
    *.log_archive_dest='/opt/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/archives'
    *.log_archive_format='PROD_%t_%s_%r.ARC'
    *.log_archive_start=TRUE
    *.open_cursors=300
    *.pga_aggregate_target=121634816
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=365953024
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='/opt/oracle/product/10.2.0/db_1/admin/ORCL/udump'
    these are contents of init+ASM.ora
    # Automatic Storage Management
    # asmallow_only_raw_disks=false
    # asm_diskgroups='TESTDB_DATA1'
    # Default asm_diskstring values for supported platforms:
    # Solaris (32/64 bit) /dev/rdsk/*
    # Windows NT/XP \\.\orcldisk*
    # Linux (32/64 bit) /dev/raw/*
    # HPUX /dev/rdsk/*
    # HPUX(Tru 64) /dev/rdisk/*
    # AIX /dev/rhdisk/*
    # asm_diskstring=''
    # Diagnostics and Statistics
    background_dump_dest=/opt/oracle/product/10.2.0/db_1/admin/+ASM/bdump
    core_dump_dest=/opt/oracle/product/10.2.0/db_1/admin/+ASM/cdump
    user_dump_dest=/opt/oracle/product/10.2.0/db_1/admin/+ASM/udump
    # Miscellaneous
    instance_type=asm
    ##compatible=10.1.0.4.0
    compatible=10.2.0.1.0
    DB_UNIQUE_NAME=+ASM
    # Pools
    large_pool_size=12M
    # Security and Auditing
    remote_login_passwordfile=exclusive
    disk groups are succcesfully configured but my database is still showing old file system.
    please guide
    Edited by: user13376823 on Oct 22, 2012 10:35 AM

  • Creating ASM disk group

    Hi,
    I have a 2-node RAC. I want to add a new diskgroup, to ASM.
    At the first node, I run the CREATE DISKGROUP command. I though the disk group would appear at second node's ASM and I would only have to mount. But on the second node EM, the disk group does not appear in V$ASM_DISK and the ALTER DISKGROUP MOUNT command returns ORA-15063.
    Do I have to create the disk at the second node too?
    Edited by: user492400 on Mar 30, 2010 12:40 PM

    how you created disks on node #1?
    did you use oracleasm createdisk command?
    run sudo /etc/init.d/oracleasm scandisk on node#1 then same command on node#2
    then run /etc/init.d/oracleasm listdisks on both nodes and compare result.
    if you see all disks correctly on both nodes, then connect to ASM on node#2 and run
    ALTER DISKGROUP ALL MOUNT;
    new diskgroup should be mounted.

  • Error while creating asm disk group:::urgent

    i am getting this error though i have given total path in DISK parameter.
    SQL> CREATE DISKGROUP dgroup1
    2 NORMAL REDUNDANCY
    3 FAILGROUP ctlr1
    4 DISK 'disk1'
    5 FAILGROUP ctlr2
    6 DISK 'disk2';
    CREATE DISKGROUP dgroup1
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15031: disk specification 'disk2' matches no disks
    ORA-15031: disk specification 'disk1' matches no disks

    hi all,
    thnx for ur attention i am able to solve the issue by doing the following steps...
    [oracle@sierra200 product]$ su - root
    Password:
    [root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk1
    [root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk2
    ioctl: LOOP_SET_FD: Device or resource busy
    [root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk1
    ioctl: LOOP_SET_FD: Device or resource busy
    [root@sierra200 root]# losetup /dev/loop2 /u04/app/oracle/product/asmdisks/disk2
    [root@sierra200 root]# vi /etc/sysconfig/rawdevices
    # raw device bindings
    # format: <rawdev> <major> <minor>
    # <rawdev> <blockdev>
    # example: /dev/raw/raw1 /dev/sda1
    # /dev/raw/raw2 8 5
    /dev/raw/raw1 /dev/loop1
    /dev/raw/raw2 /dev/loop2
    [root@sierra200 root]# /etc/init.d/rawdevices start
    Assigning devices:
    /dev/raw/raw1 --> /dev/loop1
    /dev/raw/raw1: bound to major 7, minor 1
    /dev/raw/raw2 --> /dev/loop2
    /dev/raw/raw2: bound to major 7, minor 2
    done
    [root@sierra200 root]# chown oracle:dba /dev/raw/raw1
    [root@sierra200 root]# chown oracle:dba /dev/raw/raw2
    [root@sierra200 root]# chmod 660 /dev/raw/raw1
    [root@sierra200 root]# chmod 660 /dev/raw/raw2
    [root@sierra200 root]# exit
    logout
    shut the instance and make the disk string as '/dev/raw/raw*'
    and then create spfile from pfile. and then nomount the instance.
    SQL> CREATE DISKGROUP dgroup1
    2 NORMAL REDUNDANCY
    3 FAILGROUP ctlr1
    4 DISK '/dev/raw/raw1'
    5 FAILGROUP ctlr2
    6 DISK '/dev/raw/raw2';
    Diskgroup created.
    SQL> select name, state,total_mb,free_mb,path from v$ASM_DISK;
    NAME STATE TOTAL_MB FREE_MB
    PATH
    DGROUP1_0001 NORMAL 100 50
    /dev/raw/raw2
    DGROUP1_0000 NORMAL 100 50
    /dev/raw/raw1
    Regards,
    Sravan

  • ASM disk group and multiple databases

    Hi,
    I want to create a second database on my RAC cluster. Can the ASM diskgroups I have defined for use with the first database , service the second database or do I have to create another set of ASM diskgroups for the second dataabase?
    Thanks,
    Anne

    ASM does not have any data files. ASM will store data files required for the RDBMS instance only.
    After you have installed the Oracle binaries, (best practice is to have two Oracle homes one for ASM and another for RDBMS), you can create the ASM instances using DBCA and during this process or later can create ASM diskgroups.
    ( e,g disk1G, disk2G,disk3G,disk4G) using the above four you can create ASM DISK GROUPS..

  • Create ASM disks on Solarix X64 fails with ORA-15031

    I am trying to create a ASM disk group on SOLARIS x64 using a NETAPP LUN. Below are the disks which are configured
    SQL> show parameter asm;
    NAME TYPE VALUE
    asm_diskgroups string DATA
    asm_diskstring string /dev/rdsk/c2t9*
    asm_power_limit integer 1
    asm_preferred_read_failure_groups string
    bash-3.00# ls -ltr /dev/rdsk/c2t9d0s7
    lrwxrwxrwx 1 root root 80 May 22 16:27 /dev/rdsk/c2t9d0s7 -> ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
    bash-3.00# ls -ltr ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
    crw-r----- 1 oracle dba 32, 583 May 22 16:56 ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
    I get these errors when I try to create a disk group
    SQL> create diskgroup DATA external redundancy disk '/dev/rdsk/c2t9d0s7';
    create diskgroup DATA external redundancy disk '/dev/rdsk/c2t9d0s7'
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15031: disk specification '/dev/rdsk/c2t9d0s7' matches no disks
    ORA-15025: could not open disk '/dev/rdsk/c2t9d0s7'
    ORA-15056: additional error message
    Solaris-AMD64 Error: 13: Permission denied
    Additional information: 42
    Additional information: 198045856
    Additional information: 198045848
    Please help.

    My guess is that you did not run fdisk and partition off the first 1M and ASM overwrote the VTOC rendering the device useless.
    fdisk
    create new partition
    primary partition 1
    start 2 end <last cylinder>
    Then point your disk string to these partitions (<diskname>p1?)
    Once this is done, I ALWAYS test to make sure the oracle AND grid user can read and write to this device from ALL nodes. I use the dd command to do this.
    DO NOT DO THIS ON AN ALREADY CONFIGURED AND FUNCTIONING ASM DEVICE. Doing so will erase the device.
    make a file in $HOME that contains one line:
    cat <<EOF >> $HOME/x.x
    this is a test
    EOF
    node1
    dd if=$HOME/x.x of=<disk???p1> bs=20 count=1
    node2
    dd if=<disk???p1> of=$HOME/y.y bs=20 count=1 ##y.y should be the contents of node1:x.x
    node1
    dd if=/dev/zero of=<disk???p1> bs=8192 count=1000 ## erase the device for ASM usage.
    Fix any read/write issues before proceeding.

  • 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

  • How reInstall Gride Infrastructure and Use old ASM disk groups

    <pre>Hello to all
    I installed Grig Infrastructure 11gR2 on a standalone server (OS is Linux)
    and I configured ASM and my database created on ASM
    Conceive that my OS disk corrupted and OS doesn't start and the Gride Home is on that disk,
    and I have to install OS again
    My ASM disks are safe , Now how can I install Grig Infrastructure again somehow that it can use previous ASM disks
    and disk groups and I don't oblige to create my database again ?
    In the step 2 of installing Gride Infrastructure it has four options
    <pre>
    1.Install and configure Oracle Grid Infrastructure for a Cluster
    2.Configure Oracle Grid Infrastructure for a Standalone Server
    3.Upgrade Oracle Gride Infrastructure or Oracle Automatice Storage Management
    4.Install Oracle Gride Infrastructure Software Only
    </pre>
    If I select the option 2 it wants to create a disk group again
    I guess that I need to select option 4 and then do some configuration but I don't know what I must configure
    Do you know answer of my question , if yes please explain it's stages
    Thank you so much
    </pre>

    Hi,
    no you are not obliged to recreate your database again. However there is a small flaw in the installation procedure, which does not make it 100% easy...
    When you installed the Oracle Restart (Standalone GI), your ASM diskgroup will contain the SPFILE of the ASM instance. And this is exactly the small flaw you will be encountering. So you have 2 options for "recovery":
    1.) Do a software only install (4), and run roothas.pl. This however will not create any ASM entries. You would have to add it manually (using srvctl) and you can specify the ASM Spfile with the srvctl command. Problem here is however to have to know where your ASM spfile has been. If you have a backup of your OLR and a backup of the GPNP profile, this might be easier to find out.
    2.) Do a new installation (2) and configure a new diskgroup (with a "spare" disk or small lun and a new name), that Oracle restart creates ASM instance and the new ASMSpfile for you.
    Then you can simply mount the diskgroup containing your database additionally. You then shoudl however move your new ASMSpfile to the new diskgroup (or simply exchange it with the existing one). In this case it is easier to find out where it was - however you will need a spare (though small) LUN for the new spfile (temporarily, until you exchange it).
    In either case after you have your ASM instance back (and access to your old diskgroup), you have to reregister your database and services - if you do not have an OLR backup.
    Again => It is doable and you can simply mount the ASM diskgroup containing your database. However I suggest you try this one time to know what really needs to be done in this case.
    Regards
    Sebastian

  • Difference between ASM Disk Group, ADVM Volume and ACFS File system

    Q1. What is the difference between an ASM Disk Group and an ADVM Volume ?
    To my mind, an ASM Disk Group is effectively a logical volume for Database files ( including FRA files ).
    11gR2 seems to have introduced the concepts of ADVM volumes and ACFS File Systems.
    An 11gR2 ASM Disk Group can contain :
    ASM Disks
    ADVM volumes
    ACFS file systems
    Q2. ADVM volumes appear to be dynamic volumes.
    However is this therefore not effectively layering a logical volume ( the ADVM volume ) beneath an ASM Disk Group ( conceptually a logical volume as well ) ?
    Worse still if you have left ASM Disk Group Redundancy to the hardware RAID / SAN level ( as Oracle recommend ), you could effectively have 3 layers of logical disk ? ( ASM on top of ADVM on top of RAID/SAN ) ?
    Q3. if it is 2 layers of logical disk ( i.e. ASM on top of ADVM ), what makes this better than 2 layers using a 3rd party volume manager ( eg ASM on top of 3rd party LVM ) - something Oracle encourages against ?
    Q4. ACFS File systems, seem to be clustered file systems for non database files including ORACLE_HOMEs, application exe's etc ( but NOT GRID_HOME, OS root, OCR's or Voting disks )
    Can you create / modify ACFS file systems using ASM.
    The oracle toplogy diagram for ASM in the 11gR2 ASM Admin guide, shows ACFS as part of ASM. I am not sure from this if ACFS is part of ASM or ASM sits on top of ACFS ?
    Q5. Connected to Q4. there seems to be a number of different ways, ACFS file systems can be created ? Which of the below are valid methods ?
    through ASM ?
    through native OS file system creation ?
    through OEM ?
    through acfsutil ?
    my head is exploding
    Any help and clarification greatly appreciated
    Jim

    Q1 - ADVM volume is a type of special file created in the ASM DG.  Once created, it creates a block device on the OS itself that can be used just like any other block device.  http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000
    Q2 - the asm disk group is a disk group, not really a logical volume.  It combines attributes of both when used for database purposes, as the database and certain other applications know how to talk "ASM" protocol.  However, you won't find any general purpose applications that can do so.  In addition, some customers prefer to deal directly with file systems and volume devices, which ADVM is made to do.  In your way of thinking, you could have 3 layers of logical disk, but each of them provides different attributes and characteristics.  This is not a bad thing though, as each has a slightly different focus - os file system\device, database specific, and storage centric.
    Q3 - ADVM is specifically developed to extend the characteristics of ASM for use by general OS applications.  It understands the database performance characteristics and is tuned to work well in that situation.  Because it is developed in house, it takes advantage of the ASM design model.  Additionally, rather than having to contact multiple vendors for support, your support is limited to calling Oracle, a one-stop shop.
    Q4 - You can create and modify ACFS file systems using command line tools and ASMCA.  Creating and modifying logical volumes happens through SQL(ASM), asmcmd, and ASMCA.  EM can also be used for both items.  ACFS sits on top of ADVM, which is a file in an ASM disk group.  ACFS is aware of the characteristics of ASM\ADVM volumes, and tunes it's IO to make best use of those characteristics. 
    Q5 - several ways:
    1) Connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out.  This creates an ADVM volume.  Then, format the volume using 'mkfs' (*nix) or acfsformat (windows).
    2) Use ASMCA - A gui to create a volume and format a file system.  Probably the easiest if your head is exploding.
    3) Use 'asmcmd' to create a volume, and 'mkfs' to format the ACFS file system.
    Here is information on ASMCA, with examples:
    http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348
    Information on command line tools, with examples:
    Basic Steps to Manage Oracle ACFS Systems

  • DBCA did not see the ASM disk group in NODE 2 but see in NODE 1

    Are there anyone who encountered creating a database using DBCA with ASM as file system?
    Our issue before is in both nodes the DBCA did not see the ASM disk group.
    But after setting the TNS_ADMIN in both nodes and running the DBCA as administrator in Node 1, the DBCA able to see now the ASM disk group. Unfortunately, in Node 2 it didn't work out?
    So we didn't know why is it from Node 2, the DBCA still didn't see the ASM disk group?Since it is both the same.
    Any ideas? Please advise.
    For you information, we are using Windows 64-bit, Oracle 11g R2
    Thank you in advance for those who will respond.
    Edited by: 822505 on Dec 20, 2010 7:47 PM

    822505 wrote:
    Are there anyone who encountered creating a database using DBCA with ASM as file system?
    Our issue before is in both nodes the DBCA did not see the ASM disk group.
    But after setting the TNS_ADMIN in both nodes and running the DBCA as administrator in Node 1, the DBCA able to see now the ASM disk group. Unfortunately, in Node 2 it didn't work out?
    So we didn't know why is it from Node 2, the DBCA still didn't see the ASM disk group?Since it is both the same.
    Any ideas? Please advise.
    For you information, we are using Windows 64-bit, Oracle 11g R2
    Thank you in advance for those who will respond.
    Are the disks given to the ASM are visible from Node2?
    Aman....

Maybe you are looking for

  • Carry over formatting to the next page without adding a text box

    I've written 15 books on the old pages and had no trouble carrying the formatting to the next page without adding a page or adding a text box to the added page.  I just kept on typing.  I've added the new pages and had trouble right from the start so

  • Using href in a JSP

              Hi there           I'm using to call KopfDatenJSP.jsp from another JSP, located in the package           TD/filename.jsp           DCL is the name of the application.           WLS is able to find KopfDatenJSP.jsp but its images are not dis

  • Documaker making web service calls

    Hi, does anyone know if documaker and make web service calls to retrieve data thanks

  • ClassCastException in Struts

    I have seen similar problems like this but in my case the application works fine under Tomcat but throws this exception into the bowels of struts when I make a mapping.forward() call in my struts action class. I'm sure this is a AS7 configuration iss

  • DB Adapter Polling Parameters Issues

    Hi All, We have a DB Adapter which polls on a table at every 60 seconds.we set database rows for transaction to 1 in the wizard. but when 10 records inserted into the table,DB adapter is picking up all rows at a time. this is not the expected functio