Raw Device in RAC

Hi,
I want to use Raw-Devide in RAC,
Could you Say To me That How Can We see and work with Oracle Database Files when thay are in "unformated and without letter partitions(logic part.)" in Raw-Devide ?
when Oracle begin to Format them?
Thanks a lot

If you are using raw devices, you don't see or manage files at the file system level-- you're bypassing the file system entirely. If you want to see and work with Oracle database files, you ought not be using raw devices.
Are you planning on using Oracle clustered file system or the operating system's clustering functionality for your shared storage?
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Similar Messages

  • How to create DIR/File on a raw device in RAC environment.

    Hi all,
    I use a shell script to create DIR and File on a raw device also it creates schema and tablespaces.
    I am facing problem in creating DIR and Files on raw device.
    One more thing, can multiple tablespaces be created on a raw device.
    Thanks & regards,
    Sanjeev

    Thanks for the response. Please help me further.
    About the Script - It asks for the path for creating DIR and uses shell command to create DIR. Later same path and DIR name is used to create Oracle DIR. Now in place of absolute path raw device name is passed. The same script is also used for creating tablespaces and schema.
    There is second script that is .sql script that creates external table in the newly created schema. All this has been working fine on single instance Oracle server. we have tested many times but fails in RAC environment when we use raw device.
    Question is - If I use filesystem will the external table's flat files and Directories be accessible to all the instances.
    I have one application written in java that would be clustered and running on these oracle servers. This application would be accessing those external tables and their flat files. Will there be a problem accessing these flat files accross the instances.
    Regards,
    Sanjeev.

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

  • 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

  • Raw devices versus Cluster File Systems in RAC 10gR2

    Hi,
    Does anyone using cluster file systems in a RAC 10gR2 installation, specifically IBM’s GPFS?
    I’ve visited a company that is running RAC 10gR2 in AIX over raw devices. Why someone would choose to use raw devices , with all the problems to administer , when all the modern file systems are so powerful? Is there any issues when using cluster file systems + RAC? Is there considerable performance benefits when using raw devices with RAC ?
    I´ve always used Oracle stand alone instances over file systems (since version 7) , and performance was always very good. I´ve tested raw devices almost 10 years ago , and even in that time (the hardware today is much better - SAN , 15K rpm disks , huge caches - and the file systems software today is much better) the cost to administer it does not compensate the benefits (only 5% more faster than file systems in Oracle 7).
    So , besides any limitations imposed by RAC , why use raw devices nowadays ?
    Regards,
    Antonio Belloni

    Hi,
    spontaneously, my question would be: How did you eliminate the influence of the Linux File System Cache on ext3? OCFS2 is accessed with the o_direct flag - there will be no caching. The same holds true for RAW devices. This could have an influence on your test and I did not see a configuration step to avoid it.
    What I saw, though, is "counter test": "I have tried comparing simple file copies from an OS level and the speed differences are not apparent - so the issue only manifests itself when the data is read via an oracle db." and I have no good answer to that one.
    Maybe this paper has: http://www.oracle.com/technology/tech/linux/pdf/Linux-FS-Performance-Comparison.pdf - it's a bit older, but explains some of the interdependencies.
    Last question: While you spent a lot of effort on proving that this one query is slower on OCFS2 or RAW than on ext3 for the initial read (that's why you flushed the buffer cache before each run), how realistic is this scenario when this system goes into production? I mean, how many times will this query be read completely from disk as opposed to use some block from the buffer? If you consider that, what impact does the "IO read time from disk" have on the overall performance of the system? If you do not isolate the test to just a read, how do writes compare?
    Just some questions. Thanks.

  • Is this a bug in APEX 3.0.1 Installation  RAC database with RAW device???

    Hello,
    I am getting the following error when I try to complete approval process.
    ORA-20001: Unable to create tablespace. ORA-01
    119: error in creating database file '//./FLOW_1.dbf' ORA-27040: skgfrcre: creat
    e error, unable to create file OSD-04002: unable to open file O/S-Error: (OS 2)
    The system cannot find the file specified.
    I checked the alert log for error here is the error in the alert log file.
    ORA-1119 signalled during: CREATE TABLESPACE FLOW_1 DATAFILE '//./FLOW_1.dbf'..
    and i found the syntax for create tablespace was wrong.
    To create a tablespace in RAC with RAW device environment under windows.
    it should have forward black slash instead of backward slash "/" without .dbf extension.
    so, I changed the syntax i was able to create tablespace through sqlplus.
    When APEX tool try to create this tablespace it throws this error..
    Old: CREATE TABLESPACE FLOW_1 DATAFILE
    '\\.\FLOW_1.dbf' SIZE 10304 K REUSE AUTOEXTEND OFF
    EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    error : ORA-01119: error in creating database file '\\.\FLOW_1.dbf'
    New:
    CREATE TABLESPACE FLOW_1 DATAFILE
    '\\.\FLOW_1' SIZE 10304 K REUSE AUTOEXTEND OFF
    EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    Tablespace created.
    Is it a bug in APEX 3.0.1.??
    Is anyone installed APEX in RAC ??
    James

    Hi,
    One observation, Apex is switching the Session ID after one got killed ? I was working on Apex page with browse Item to test open cursor count,
    after killing the SID (227) on which the open cursor count was getting increase, it APEX automatically switches to new SID(149) for that session.
    Now the problem is even if I have two SID's and one hits the maximum open cursor count, It is not switching to other SID instead the whole application becomes unavailable.
    STATNAME SID VALUE USER
    opened cursors current 20 14 APEX_PUBLIC_USER
    opened cursors current 149 74 APEX_PUBLIC_USER
    opened cursors current 194 71 APEX_PUBLIC_USER
    opened cursors current 211 5 APEX_PUBLIC_USER
    opened cursors current 227 325 APEX_PUBLIC_USER Killed
    opened cursors current 244 15 APEX_PUBLIC_USER
    opened cursors current 20 14 APEX_PUBLIC_USER
    opened cursors current 149 76 APEX_PUBLIC_USER
    opened cursors current 194 71 APEX_PUBLIC_USER
    opened cursors current 211 5 APEX_PUBLIC_USER
    opened cursors current 244 15 APEX_PUBLIC_USER
    Please kindly help in this.
    Thanks in Advance
    Thanks & Regards
    Sanjay
    Edited by: user11204334 on Dec 8, 2010 1:02 AM

  • Create a physical standby for Rac on Windows and raw devices

    Hi buddies:
    I need to create a Physical standby database for a 2 node RAC cluster on Windows, that is using RAW devices.
    Can someone of you suggest me a note to follow in order to achive this, i can not find to much information about how to do this.
    I guess that the best option would be to use RMAN to do this, but as i said before i havent found too much information.
    I would really appreciate your help.
    Kind regards
    MQ

    In this case the standby should be created as a single instance on regular files.
    Do i have to specify something different in the duplicate rman command to specify that the standby database will be a single instance?
    Thanks for your help
    MQ

  • Root.sh failed:Raw devices for OEL 5.3 and 10.2.0.4 RAC

    Hi
    We have OEL 5.3 and Oracle RAC 10.2.0.4
    While installing clusterware and running root.sh we are getting the error
    Failed to upgrade the cluster registry.
    Further the ocrconfig.log are as below:
    ocrconfig_20527.log
    Oracle Database 10g CRS Release 10.2.0.1.0 Production Copyright 1996, 2005 Oracle. All rights reserved.
    2009-08-04 04:38:41.540: [ OCRCONF][286303376]ocrconfig starts...
    2009-08-04 04:38:41.540: [ OCRCONF][286303376]Upgrading OCR data
    2009-08-04 04:38:41.615: [  OCRRAW][286303376]propriogid:1: INVALID FORMAT
    2009-08-04 04:38:41.616: [  OCRRAW][286303376]ibctx:1:ERROR: INVALID FORMAT
    2009-08-04 04:38:41.616: [  OCRRAW][286303376]proprinit:problem reading the bootblock or superbloc 22
    2009-08-04 04:38:41.616: [ default][286303376]a_init:7!: Backend init unsuccessful : [22]
    2009-08-04 04:38:41.616: [ OCRCONF][286303376]Exporting OCR data to [OCRUPGRADEFILE]
    2009-08-04 04:38:41.616: [  OCRAPI][286303376]a_init:7!: Backend init unsuccessful : [33]
    2009-08-04 04:38:41.616: [ OCRCONF][286303376]There was no previous version of OCR. error:[PROC-33: Oracle Cluster Registry is not configured]
    2009-08-04 04:38:41.619: [  OCRRAW][286303376]propriogid:1: INVALID FORMAT
    2009-08-04 04:38:41.619: [  OCRRAW][286303376]ibctx:1:ERROR: INVALID FORMAT
    2009-08-04 04:38:41.619: [  OCRRAW][286303376]proprinit:problem reading the bootblock or superbloc 22
    2009-08-04 04:38:41.619: [ default][286303376]a_init:7!: Backend init unsuccessful : [22]
    2009-08-04 04:38:41.623: [  OCRRAW][286303376]propriogid:1: INVALID FORMAT
    2009-08-04 04:38:41.623: [  OCRRAW][286303376]ibctx:1:ERROR: INVALID FORMAT
    2009-08-04 04:38:41.623: [  OCRRAW][286303376]proprinit:problem reading the bootblock or superbloc 22
    2009-08-04 04:38:41.626: [  OCRRAW][286303376]propriogid:1: INVALID FORMAT
    2009-08-04 04:38:41.641: [  OCRRAW][286303376]propriowv: Vote information on disk 0 [dev/raw/raw1] is adjusted from [0/0] to [2/2]
    2009-08-04 04:38:41.646: [  OCRRAW][286303376]propriniconfig:No 92 configuration
    2009-08-04 04:38:41.646: [  OCRAPI][286303376]a_init:6a: Backend init successful
    2009-08-04 04:38:41.663: [ OCRCONF][286303376]Initialized DATABASE keys in OCR
    2009-08-04 04:38:41.677: [ OCRCONF][286303376]csetskgfrblock0: clsfmt returned with error [4].
    2009-08-04 04:38:41.677: [ OCRCONF][286303376]Failure in setting block0 [-1]
    2009-08-04 04:38:41.677: [ OCRCONF][286303376]OCR block 0 is not set !
    2009-08-04 04:38:41.678: [ OCRCONF][286303376]Exiting [status=failed]...
    Any solution please?
    Supriya Sh

    There are a couple of errors that doesn't make the clusterware look fine.
    There was no previous version of OCR. error:PROC-33: Oracle Cluster Registry is not configured
    proprinit:problem reading the bootblock or superbloc 22
    This could mean either your cluster registry file is corrupt or you don't have access to the raw devices. Check the access to the shared storage raw device is valid. If this is not true, then make sure you have all your backup files ready.
    ~ Madrid
    http://hrivera99.blogspot.com

  • Oracle 9.2 RAC installation error on raw devices

    During Oracle 9.2 RAC installation on Linux Red Hat 7.3 on raw devices
    Database Configuration Assistant
    returned the error message:
    "Raw device validation check for Data File
    "/dev/raw/clustdb_raw_cwmlite_100m" failed, No such file or directory".
    Really this file exists, this is a link to a raw device.
    How does Oracle validate the raw file?
    What does this error mean?
    Igor.

    During Oracle 9.2 RAC installation on Linux Red Hat 7.3 on raw devices
    Database Configuration Assistant
    returned the error message:
    "Raw device validation check for Data File
    "/dev/raw/clustdb_raw_cwmlite_100m" failed, No such file or directory".
    Really this file exists, this is a link to a raw device.OK, so you are saying that /dev/raw/clustdb_raw_cwmlite_100m is link to /dev/raw/raw<x> (x some number)??
    If not - there is your error.
    How does Oracle validate the raw file?File MUST exists (or link) AND it must be a RAW device.
    You can check it by raw -qa (it should display all raw devices, with theirs major-minor pairs)
    What does this error mean?
    Igor. Hrvoje

  • 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

  • RAC on RAW device

    1) Hi I am configuring rac on raw device 9i on aix5.Whether i can create a datafile morethan 1 gb in raw device.Can anybody give one example with creating a tablespace with a raw device configuration.The steps have to follow
    2) why we cannot store archivelogs on rawdevices
    with regards
    ramya

    1)Whether we can store RMAN backup on RAW devices .
    Answer : Yes, you can, just create the raw partition and point out the destination when you use the rman command. or you can take a backup to the local file system first and then move to raw device.
    2)whether we can do the export on RAW devices
    Answer : Same as No.1
    3) Whether we can create a 2gb datafile on RAW devices
    Answer : Yes, you can.
    I hope it would be helpful to you.

  • 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

  • Raw device valiadation during dbca RAC installation

    When i am trying to create Cluster DB by using dbca, i received
    "Raw device validation check for control file /var/opt/oracle/oradata/orcl/Control01.ctl" failed stat for /var/opt/oracle/oradata/orcl/Control01.ctl file failed.
    Any idea about this error........
    My Env: oracle 9.2.0.4, RH 2.1AS, OCFS.
    Thanks.

    I followed metalink Doc ID:217319.1 Raw Device Validation Check When Using DBCA to Create a RAC Databae.
    but no use.
    Any idea why i am getting this error.
    Thanks.

  • Raw devices for 11g rac

    hi,
    whether 11gr2 rac supports raw devices in ibm aix 6.1 with power ha?
    regards
    sridhar

    Hi;
    Pelase see:
    Raw Devices and Cluster Filesystems With Real Application Clusters (RAC) [ID 183408.1]
    For your future RAC related issue I suggest close your issue here as answered than move your issue Forum Home » High Availability » RAC, ASM & Clusterware Installation which is RAC dedicated forum site.
    Regard
    Helios

  • OPS/RAC Vs Raw Device/File System

    Hello, firts to all, I want to know what is OPS/RAC and Raw Device/File System.
    And then know the diferens between both.
    I apologize for my english.
    Thanks.

    OPS is Oracle parallel server was available up to Oracle 8i and RAC is Real application cluster is available from Oracle 9i.
    Raw device is just presenting the disk to server and using it. File system is presenting disk more transparent and managable form using OS or third party software.
    You need to refer respective documents to know them in detail.
    Ashok

Maybe you are looking for