ASM Spfile on shared raw device

Hi,
I am building two nodes Cluster on Linux 4 update 5. I have successfully created the CRS. Now I am trying to create the ASM instance using the ./dbca. When I select both nodes to manage diskgroup, during the instance creation, and after I enter the SPFILE file location, I am receiving this message
{The /dev/raw/raw10/spfile.asm.ora location is not valid. The directory "[/dev/raw/raw10/] is not a shared system partition across nodes1 and 2.}
The Oracle:dba has the ownership and read/write permission on this partition.
Your help highly appreciated.
Majid

1) Check to make sure that the partition /dev/raw/raw10 is a shared raw device between the nodes (you can do this by using: dd if=/dev/zero of=/dev/raw/raw10 bs=1M count=x from both the nodes while logged in oracle).
2) Since /dev/raw/raw10 is a raw device, you can not specify /dev/raw/raw10/spfile.asm.ora as an SPFILE location. Alternatively, under $ORACLE_HOME/dbs create a link to /dev/raw/raw10 with the name spfile$ORACLE_SID.ora from both the nodes.
ln -s /dev/raw/raw10 $ORACLE_HOME/dbs/spfile$ORACLE_SID.ora (both the nodes)
HTH
Thanks
Chandra

Similar Messages

  • SPARC 64bit Clusterware 10.2.0.4 - shared raw device

    Dear group,
    I have been asked to install RAC 10.2.0.4 SE on Solaris 10 (SPARC). I am not a Solaris admin altough I have done many RAC installations on RHEL4/5.
    Does anyone have suggestions/pointers to documentation (apart from the docs on OTN which I already consulted) on how to place OCR and vorting disk on shared raw devices? The setup is unlikely to use any multipathing but will rely on a low end SAN for shared storage. I am especially interested in the proper use of the "format" tool (I know for instance that I need to start from cyliner 1 for ASM slices).
    So far all I found were documents explaining SFRAC, Sun Cluster etc which I either don't have at my disposal or can't use due to license restrictions.
    On a comparable single-pathing Linux setup, we'd simply use fdisk to create partitions on the shared disk(s) which then are made available as raw devices thanks to udev.
    Thanks and regards,
    Martin

    Hi Martin,
    Take a look on this doc http://download.oracle.com/docs/cd/B19306_01/install.102/b14205/storage.htm#sthref675
    Regards,
    Rodrigo Mufalani
    http://mufalani.blogspot.com

  • Shared raw devices not discover during Oracle11g r2 RAC/Grid Installations

    Dear Gurus
    Our Platform: Redhat Linux Enterprise Editions5.3 64bit
    We are installing Oracle11g r2 Grid(Clusterware+ASM) and want to use ASM for storage OCR,VOTING,DATA and FLASH Storage.
    We are not want to use ASMLib.
    plz find the shared raw partitions details
    RAC Node-1
    [root@xyz-ch-aaadb-01 ~]# fdisk -l
    Disk /dev/sda: 145.9 GB, 145999527936 bytes
    255 heads, 63 sectors/track, 17750 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 13 104391 83 Linux
    /dev/sda2 14 6540 52428127+ 83 Linux
    /dev/sda3 6541 11370 38796975 83 Linux
    /dev/sda4 11371 17750 51247350 5 Extended
    /dev/sda5 11371 17358 48098578+ 82 Linux swap / Solaris
    /dev/sda6 17359 17750 3148708+ 83 Linux
    Disk /dev/sdb: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdc: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdd: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdd1 1 66837 536868171 83 Linux
    Disk /dev/sde: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sde1 1 66837 536868171 83 Linux
    Disk /dev/sdf: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdf1 1 66837 536868171 83 Linux
    Disk /dev/sdg: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    /dev/sdg1 1 1014 3143369 83 Linux
    Disk /dev/sdh: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdh1 1 66837 536868171 83 Linux
    RAC Node-2
    [root@xyzl-ch-aaadb-02 ~]# fdisk -l
    Disk /dev/sda: 145.9 GB, 145999527936 bytes
    255 heads, 63 sectors/track, 17750 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 13 104391 83 Linux
    /dev/sda2 14 6540 52428127+ 83 Linux
    /dev/sda3 6541 11240 37752750 82 Linux swap / Solaris
    /dev/sda4 11241 17750 52291575 5 Extended
    /dev/sda5 11241 15940 37752718+ 83 Linux
    /dev/sda6 15941 16332 3148708+ 83 Linux
    Disk /dev/sdp: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdq: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdr: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdr1 1 66837 536868171 83 Linux
    Disk /dev/sds: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sds1 1 66837 536868171 83 Linux
    Disk /dev/sdt: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdt1 1 66837 536868171 83 Linux
    Disk /dev/sdu: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    /dev/sdu1 1 1014 3143369 83 Linux
    Disk /dev/sdv: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdv1 1 66837 536868171 83 Linux
    Disk /dev/sdw: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdx: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdy: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdy1 1 66837 536868171 83 Linux
    Disk /dev/sdz: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdz1 1 66837 536868171 83 Linux
    Disk /dev/sdaa: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdaa1 1 66837 536868171 83 Linux
    Disk /dev/sdab: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    /dev/sdab1 1 1014 3143369 83 Linux
    Disk /dev/sdac: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdac1 1 66837 536868171 83 Linux
    plz suggest the solutions.....
    Edited by: hitgon on Aug 20, 2011 3:49 AM
    Edited by: hitgon on Aug 20, 2011 3:50 AM

    we are still not able to discover the shared raw device partitions,
    plz help us......
    now my fdisk -l shown the shown the consistent raw device partitions
    plz find the details...........
    [root@xyz-ch-aaadb-01 grid]# fdisk -l
    Disk /dev/sda: 145.9 GB, 145999527936 bytes
    255 heads, 63 sectors/track, 17750 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 13 104391 83 Linux
    /dev/sda2 14 6540 52428127+ 83 Linux
    /dev/sda3 6541 11370 38796975 83 Linux
    /dev/sda4 11371 17750 51247350 5 Extended
    /dev/sda5 11371 17358 48098578+ 82 Linux swap / Solaris
    /dev/sda6 17359 17750 3148708+ 83 Linux
    Disk /dev/sdb: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdc: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdd: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdd1 1 66837 536868171 83 Linux
    Disk /dev/sde: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sde1 1 66837 536868171 83 Linux
    Disk /dev/sdf: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdf1 1 66837 536868171 83 Linux
    Disk /dev/sdg: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    /dev/sdg1 1 1014 3143369 83 Linux
    Disk /dev/sdh: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdh1 1 66837 536868171 83 Linux
    RAC Node-2
    [root@xyz-ch-aaadb-02 ~]# fdisk -l
    Disk /dev/sda: 145.9 GB, 145999527936 bytes
    255 heads, 63 sectors/track, 17750 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 4700 37752718+ 83 Linux
    /dev/sda2 4701 11227 52428127+ 83 Linux
    /dev/sda3 11228 11619 3148740 83 Linux
    /dev/sda4 11620 17750 49247257+ 5 Extended
    /dev/sda5 11620 17750 49247226 83 Linux
    Disk /dev/sdb: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdc: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    Disk /dev/sdd: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdd1 1 66837 536868171 83 Linux
    Disk /dev/sde: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sde1 1 66837 536868171 83 Linux
    Disk /dev/sdf: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdf1 1 66837 536868171 83 Linux
    Disk /dev/sdg: 3221 MB, 3221225472 bytes
    100 heads, 62 sectors/track, 1014 cylinders
    Units = cylinders of 6200 * 512 = 3174400 bytes
    Device Boot Start End Blocks Id System
    /dev/sdg1 1 1014 3143369 83 Linux
    Disk /dev/sdh: 549.7 GB, 549755813888 bytes
    255 heads, 63 sectors/track, 66837 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sdh1 1 66837 536868171 83 Linux
    find the following details.........
    ===============================================
    RAC Node-1
    [root@xyz-ch-xxxdb-01 grid]# ls -l /dev/sdb
    brw-r----- 1 root disk 8, 16 Aug 19 09:15 /dev/sdb
    [root@xyz-ch-xxxdb-01 grid]#
    [root@xyz-ch-xxxdb-01 grid]# ls -l /dev/sdg
    brw-r----- 1 root disk 8, 96 Aug 19 09:15 /dev/sdg
    RAC Node-2
    [root@xyz-ch-xxxdb-02 ~]# ls -l /dev/sdb
    brw-r----- 1 root disk 8, 16 Aug 19 18:41 /dev/sdb
    [root@xyz-ch-xxxdb-02 ~]#
    [root@xyz-ch-xxxdb-02 ~]#
    [root@xyz-ch-xxxdb-02 ~]# ls -l /dev/sdg
    brw-r----- 1 root disk 8, 96 Aug 19 18:41 /dev/sdg
    Edited by: hitgon on Aug 20, 2011 3:50 AM

  • ASM cannot find the raw devices nor ASM drives

    Hi,
    We are trying to use ASM on linux. The kernel version is
    2.6.9-42.0.10.0.1.ELsmp x86_64.
    We tried both raw devices and ASM drives. But after all the tries, the installer simply will not list the disks.
    Anybody can help? Thanks.

    "I had installed ASM initially on the same CRS, but due to some error during the installation"
    This statement means: I had installed ASM on the clusterware, but due to time synchronization error, it didn't got copied on to the 2nd node, and hence I had to uninstall the ASM software.
    But the clusterware is still up and running.
    Amit.

  • ASM spfile on raw device

    How do you create a spfile on a raw device, or how do you move one to it?
    Any help will be appreciated.
    Thanks

    Hi all,
    maybe I am the only one, but as I understood Alexander's question, he wants to put the ASM spfile on a RAW device, not the database spfile - but I might be wrong. Alexander?
    An ASM spfile cannot be kept in a diskgroup. However, if you choose to manage the ASM environment using DBCA, you can specify a shared location for the ASM spfile in course of the initialization of the ASM environment (when you create your ASM instances for the first time using DBCA).
    Once the ASM environment has been created, one may use Ned's approach to relocate a spfile of an ASM environment as well. I am not too sure, but I would think that the sqlplus command "create spfile='RAW device' from pfile; would do the trick, too, given that you have a pfile. Now, if you have a spfile only right now, you can create a pfile first using this command and create the spfile in the final destination later. However, in either case, do not forget to change the pfile link after you have performed those steps.
    Just my 2 cents. Thanks,
    Markus

  • ASM support BLOCK raw device?

    Does ASM support for BLOCK raw device? or only there is support for CHARACTER raw device?
    Or it is specific to UNIX platforms?
    Thanks.

    790066 wrote:
    Does ASM support for BLOCK raw device? or only there is support for CHARACTER raw device?As I understand, ASM needs to be able to open a device using the direct I/O call kernel interface. Old style block devices do not have that, thus the need for raw char devices (on top of a block device) to provide the required direct I/O interface.
    But raw devices have been depreciated by the Linux kernel and Oracle also has support notes stating the same. The kernel now supports opening a block device with the O_DIRECT flag set.
    Offhand though, I do not see a problem using a device in ASM as long as ASM has access to it (permissions okay, discovery string set) and the device can be successfully opened via the I/O calls made by ASM.
    You need to select the most appropriate device interface (if a device has multiple) for ASM to use. I'll expect that ASM notes/installation details from Oracle for that specific o/s will have the details needed to make that decision.
    Or it is specific to UNIX platforms?Do not use anything else but Linux for many years now, so cannot comment on how this works/looks like on Unix flavours like Solaris and HP-UX and others.

  • Raw Device Validation Check for Name Failed..

    Hi all,
    I have installed Oracle Clusterware 10.2.0.4 and Oracle database software 10.2.0.4 on Solaris SPARC 10 and i using a NAS storage for the same
    And when i try to create a database using DBCA i got the following error.
    Raw Device Validation Check for Name /u03/oradata/spfile/spfile{SID}.ora failed. The specified file /u01/oradata/spfile/spfile{SID}.ora doesnot exit.Please a existing file.
    Note: i am not using ASM., i am using RAW device for Database
    Any help highly thankful
    -Arun

    Hi
    this is how i have mounted the NAS...
    10.0.0.0:/vol/prodt3_vol16/ora_dbfr_inn1s - /u07/DBFR/INS nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,forcedirectio,vers=3,suid
    how do i ensure that it is not being used....we should not use ASM its an client requinment ...
    Thanks

  • How to determine raw disks configured for OCR/voting disk, ASM spfile

    I have a two-node Oracle 10gR2 RAC configuration using raw disks. Basically, raw disks are used for CRS's OCR/voting disks, ASM's ASM spfile and disk groups.
    Is there a better way to figure out what raw disks are configured in Oracle using methods other than those shown below:
    - To find out votedisk:
    # crsctl query css votedisk
    0. 0 /dev/ora_crs_vote1
    1. 0 /dev/ora_crs_vote2
    2. 0 /dev/ora_crs_vote3
    - To find out OCR:
    # ocrcheck
    Status of Oracle Cluster Registry is as follows :
    Version : 2
    Total space (kbytes) : 525836
    Used space (kbytes) : 3856
    Available space (kbytes) : 521980
    ID : 1603037329
    Device/File Name : /dev/ora_ocr_file1
    Device/File integrity check succeeded
    Device/File Name : /dev/ora_ocr_file2
    Device/File integrity check succeeded
    Cluster registry integrity check succeeded
    - Is there a way to figure out what disk device is used for ASM spfile?
    - To find out raw disks configured for disk groups:
    while connected to the ASM instance in sqlplus:
    SQL> select name,path from v$asm_disk where name like 'DG%';
    NAME
    PATH
    DG_DC_ASM_0000
    /dev/rhdiskpower13
    DG_DC_ASM_0001
    /dev/rhdiskpower14
    DG_DC_ASM_0002
    /dev/rhdiskpower15
    NAME
    PATH
    DG_DC_ASM_0003
    /dev/rhdiskpower22

    http://docs.oracle.com/cd/B19306_01/install.102/b14203/storage.htm#BABFFBBA
    and
    Configuring raw devices (singlepath) for Oracle Clusterware 10g Release 2 (10.2.0) on RHEL5/OEL5 [ID 465001.1]
    Configuring raw devices (multipath) for Oracle Clusterware 10g Release 2 (10.2.0) on RHEL5/OEL5 [ID 564580.1]

  • 10g ASM on Logical Volumes vs. Raw devices and SAN Virtualization

    We are looking at setting up our standards for Oracle 10g non-rac systems. We are looking at the value of Oracle ASM in our environment.
    As per the official Oracle documentation, raw devices are preferred to using Logical Volumes when using ASM.
    From here: http://download.oracle.com/docs/cd/B19306_01/server.102/b15658/appa_aix.htm#sthr
    ef723
    "Note: Do not add logical volumes to Automatic Storage Management disk groups. Automatic Storage Management works best when you add raw disk devices to disk groups. If you are using Automatic Storage Management, then do not use LVM for striping. Automatic Storage Management implements striping and mirroring."
    Also, as per Metalink note 452924.1:
    "10) Avoid using a Logical Volume Manager (LVM) because an LVM would be redundant."
    The issue is: if we use raw disk devices presented to ASM, the disks don't show up as used in the unix/AIX system tools (i.e. smit, lspv, etc.). Hence, when looking for raw devices on the system to add to filesystems/volume groups/etc., it's highly possible that a UNIX admin will grab a raw device that is already in use by Oracle ASM.
    Additionally, we are using a an IBM DS8300 SAN with IBM SAN Volume Controller (SVC) in front of it. Hence, we already have storage virtualization and I/O balancing at the SAN/hardware level.
    I'm looking for a little clarification to the following questions, as my understanding of their responses seem to confict:
    QUESTION #1: Can anyone clarify/provide additional detail as to why Logical volumes are not preferred when using Oracle ASM? Does the argument still hold in a SAN Virtualized environment?
    QUESTION #2: Does virtualization at the software level (ASM) make sense in our environment? As we already have I/O balancing provided at the hardware level via our SVC, what do we gain by adding yet another level of I/O balancing at the ASM level? Or as in the
    arguments the Oracle documentation makes against using Lvm, is this an unnecessary redundant striping (double-striped or in our case triple-striped/plaid)?
    QUESTION #3: So does SAN Virtualization conflict or compliment the virtualization provided by ASM?

    After more research/discussions/SR's, I've come to the following conclusion.
    Basically, in an intelligent storage environment (i.e. SVC), you're not getting a 100% bang for the buck by using ASM. Which is the cat's meow in a commodity hardware/unintelligent storage environment.
    Using ASM in a SVC environment potentially wastes CPU cycles having ASM balance i/o that is already balanced on the backend (sure if you shuffle a deck of cards that are already shuffled you're not doing any harm, but if they're already shuffled - then why are you shuffling them again??).
    That being said, there may still be some value for using ASM from the standpoint of storage management for multiple instances on a server. For example, one could better minimize space wastage by being able to share a "pool" of storage between mulitiple instances, rather than having to manage space on an instance-by-instance (or filesystem by filesystem) level.
    Also, in the case of having a unfriendly OS where one is unable to dynamically grow a filesystem (i.e. database outage required), there would be a definite benefit provided by ASM in being able to dynamically allocate disks to the "pool". Of course, with most higher-end end systems, dynamic filesystem growth is pretty much a given.
    In the case of RAC, regardless of the backend, ASM with raw is a no-brainer.
    In the case of a standalone instance, it's a judgement call. My vote in the case of intelligent storage where one could dynamically grow filesystems, would be to keep ASM out of the picture.
    Your vote may be different....just make sure you're putting in a solution to a problem and not a solution that's looking for a problem(s).
    And there's the whole culture of IT thing as well (i.e. do your storage guys know what you're doing and vice versa).....which can destroy any technological solution, regardless of how great it is.

  • 10.1.0.3 on RH4(Centos) + Raw devices + ASM + RAC

    Hi,
    I'm just wondering if anyone here tried installing a single node RAC on 2 instance using ASM on Oracle 10g (10.1.0.3)?
    I am using RH4(CENTOS 4.1), Oracle 10.1.0.3 + CRS 10.1.0.3 on fake raw devices in Linux.
    I have been able to install the CRS and Oracle database software successfully.
    All CRS services and listener are up and running.
    crs_stat command return successful results.
    srvctl status nodeapps -n <node_name> also returns successful results.
    However, when I attempt to startup the ASM instance, I keep encountering these errors:
    ORA-00603:ORACLE server session terminated by fatal error
    ORA-27504:IPC error creating OSD context
    The ORA-00603 error message will appear immediately in the SQLPLUS prompt when I try to startup ASM instance.
    Both errors will be logged in alert.log and trace files, no other useful error messages besides these errors.
    When I attempt to create a normal database instance using datafiles on the same machine, these errors also appear again!
    So, I figure its got nothing to do with the raw devices since my OCR location and Voting devices are using the same raw devices on Linux.
    Anyone did the same thing like me and faced similar problems.... please help.
    Cheers

    You can use dbca to create ASM instance to get rid of the manual copy business.
    In realease 1, you can invoke dbca, choose database instance and walk through still you reach storage clause and choose asm and DBA will create ASM instance on both nodes.
    Ensure that you choose cluster install option and all the nodes at the initial stages.

  • Is database using File system, RAW devices or ASM?

    Hi there
    Is is possible to find out if the database is using File system, RAW devices or ASM for storage?
    I think for ASM, we can tell by querying the V$DATAFILE view if it has ' DATA ' or something like that (a name that has ' ' prefixed to it). Is this the only way? How about other sotrage types (RAW and Filesystem)?
    Thanks in advance!

    user12033597 wrote:
    I think for ASM, we can tell by querying the V$DATAFILE view if it has ' DATA ' or something like that (a name that has ' ' prefixed to it). Is this the only way? How about other sotrage types (RAW and Filesystem)?V$DATAFILE or DBA_DATA_FILE
    Raw depends on your OS - in *nix, likely something like /dev/sdc1
    ASM depends on ASM and will include + and will follow an ASM pattern, such as described http://docs.oracle.com/cd/B19306_01/server.102/b14200/clauses004.htm
    File depends on OS - in *nix, likely start with a '/' and NOT be in /dev or /proc.  In Winders start with C:\ or some other disk path.
    Nicely discussed in the docs in the Administrators Guide found at http://tahiti.oracle.com

  • Question(s) related to ASM, Raw devices and performance

    Good morning,
    I was recently getting acquainted with ASM. Since I was doing this in "play" VM boxes, it was not possible to draw any conclusions about any performance improvements.
    I'd like to know what performance improvements forum members may have experienced after migrating a production environment from a non-ASM setup to an ASM setup.
    It would seem that since ASM is a "form" of raw device access that the increase in performance should be noticeable. Was that the case for those who migrated to it ? Was the performance improvement worth it or did it only make managing the database easier ?
    Thank you for your contributions on the subject,
    John.

    ASM uses disk groups to store datafiles; an ASM disk group is a collection of disks that ASM manages as a unit. Within a disk group, ASM exposes a file system interface for Oracle database files. The content of files that are stored in a disk group are evenly distributed, or striped, to eliminate hot spots and to provide uniform performance across the disks. The performance is comparable to the performance of raw devices.
    You can add or remove disks from a disk group while a database continues to access files from the disk group. When you add or remove disks from a disk group, ASM automatically redistributes the file contents and eliminates the need for downtime when redistributing the content.
    I hope the links below will helps you.
    refer the links:
    http://download.oracle.com/docs/cd/B28359_01/server.111/b31107/asmcon.htm
    http://oracleinstance.blogspot.com/2009/12/rac-file-system-options-basic-concept.html
    http://www.dbasupport.com/oracle/ora10g/ASM01.shtml
    also you will get more information from book:
    Oracle Automatic Storage Management: Under-the-Hood & Practical Deployment Guide (Osborne ORACLE Press Series)
    Nitin Vengurlekar (Author), Murali Vallath (Author), Rich Long (Author)
    http://www.amazon.com/Oracle-Automatic-Storage-Management-Under/dp/0071496076

  • Oracle rac raw device as shared storage

    Hi,
    i m new to oracle rac,
    and i wish to instlall 11g r1 RAC on my laptop having linux 4 as platform (on vmware) ,
    for that i prepare 4 partition for that (on node1)
    /dev/sdb1 - for ocr
    /dev/sdb2 - for voting disk
    /dev/sdb3 - for asmdisk group
    /dev/sda5 - fro asmdisk group
    by assuming external redundacy for ocr and voting disk i kept only one disk
    and i configured following in /etc/sysconfig/rawdevices
    /dev/raw/raw1 /dev/sdb1 -- ocr
    /dev/raw/raw2 /dev/sdb2 -- voting disk
    /dev/raw/raw3 /dev/sdb3 -- asmdisk group
    /dev/raw/raw4 /dev/sdb5 -- asmdisk group
    and my question is how node2 can understat these raw device as shared storage?
    thanks for any support

    hi thanks for your suggestion ,
    this may be ok for VMware , but what about for non-VMWare environment?
    how can i make raw device as shared storage?
    one more, all the docs that i followed on net , configured node1 partitions as shared storage.
    please help me in this regards

  • How to check space on asm and raw device?

    Hi All,
    I want to know how to check the space on asm device.
    we are using asm device which is on raw partition.
    Our archive gets full.I need to check the space on asm archve partiotion.
    how can i check the archive destination space?
    we are using raw device partition for crs and voting device.
    how can we check the space on raw device and how can we know which device is in use and which are not in use
    Thanks in advance

    4 - 5 raw partitions...
    What oracle version?
    Install OCR + VOTE in raw device better than OCFS2. if you use 10g to 11gR1.
    If use 11gR2,keep OCR + VOTE in ASM Disk Group.
    you can check which raw device OCR:
    $ ocrcheck
    VOTEDISK:
    $ crsctl query css votedisk
    On 10g if use raw device for OCR + votedisk: recommend 1 file = 250M
    11g recommend 1 file = 512M
    Good Luck

  • Reinstall DB and ASM using existing RAW devices in RAC

    Hi,
    We have two Database servers in Cluster environment DB1 and DB2 using CX300(SAN) as Storage device.Recently we had upgraded the OS kernel on DB1 from RHEL 3 to RHEL 4 and DB2 is still running on RHEL 3. Due to some application problems we wanted the DB1 to be rollbacked to RHEL 3
    DB1-has ASM1 instance and DB2 has ASM2 instance running.Similary SID1 and SID2 on both of them.
    Since we want to roll back to RHEL 3 it is a clean install on DB1. So my problem is I had never done this kind of reinstallation of DB and ASM using existing raw devices.
    Can Someone sent me out some instructions and steps on how to do the reinstall without disturbing RAC,DB2 and Data on RAW/CX300(SAN) device.
    I am basically a system admin not a complete Oracle DBA.I will be grateful for your help.
    Thanks,
    Shiva

    It means, before proceeding a proper database backup must be taken, then it has to be started from scratch. RHEL3 is certified with 10gR1 and 10gR2, you should be aware of the patchsets available for the oracle version.
    I suggest you to read the Clusterware and RDBMS installation guides:
    Oracle® Database Release Notes
    10g Release 2 (10.2) for Linux x86
    B15659-03
    Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide
    10g Release 2 (10.2) for Linux
    Part Number B14203-08
    Installing Oracle RAC 10g Release 2 on Linux x86
    ~ Madrid

Maybe you are looking for

  • PDF file doesn't view properly in firefox & favicon doesn't show in Safari

    I've got three issues I could use some advice with. 1. I used some iFrame code generously posted by Oldtoad that allows a pdf file in an IFrame. It works beautifully in Safari. here's an example: http://web.mac.com/phelpssculpture/Site/resumeone_page

  • Choices for free goods determination

    Hi all, I want to have choices for free goods determination, like for Material A I want an option to select either of Material A or B. Is this possible. regards, Vandana Arora

  • Looking for some Flash tutorials

    I'm doing some webstuff in Flash CS5 using actionscript 3, and I could use some help with a couple of things.  Can anyone recommend some tutorials on how to make an effective image gallery?  Like with a picture slider or something?  But ideally nothi

  • How to restrict RFBILA00 to company codes

    Hello, I am still a SAP-rookie, so maybe you can help me. My problem is that in my company we have different users with different company codes using RFBILA00. How can I limit the RFBILA00 only for the company code of the current user? - (SAP Release

  • Matrix  Report ...Heading Overflow

    Hi All: I have to create a matrix report in following format which display total depending on row & column Designation Lab Assistant Lab Technician Teacher Teacher Assistant Department Physics        2                     1                  1