Question on raw device names in Solaris

DB Version :11G Release 2
OS : Solaris 5.10 (AMD x86)
Number of Nodes:2
I've finished installing Grid infrastructure and RDBMS software. I have invoked ASCMA (GUI) to create disk groups. ASMCA has succesfully listed the Disk group i've created for OCR and Voting Disk during Grid Installation. Now it is time to create the Disk group for Datafiles.
Storage Admins have given us a shared Slice of 700GB for this test installation.
This slice seen from Node1:
/dev/rdsk/c3t400A0B800047D3M3210s3The same slice seen from Node2
/dev/rdsk/c1t400A0B800038A4CA0050s3From Google and OTN, If i understand correctly, you need a 'multi-pathing disk driver' to make these slices appear with one name. I don't think we have this in our site.
Invoking ASMCA gui from Node1, I've just succesfully created a Disk group called DG1 from the 700 GB slice mentioned above. But, how will i let Node2 know that the slice which DG1 is made of (c3t800A0B800047D3M3210s3 when seen from Node1) is acutually the same 700 GB slice known to Node2 as
c1t400A0B800038A4CA0050s3?
Should i invoke ASMCA from node2 and do something to let node2 know about this? I can set
ASM_DISKSTRING=/dev/rdsk/c1*from Node2's ASM instance. But there other slices appearing in Node2 starting with
c1*How will Node2 correctly discover the 700 gb c1****s3 shared slice meant for this RAC installation? What is point of setting ASM_DISSTRING anyway? I mean, we might be able to get node2 slice names on ASMCA's list. But, it is the same slice appearing as a different name. So , there is no point in ticking (the check box in GUI) it anyway.
Should i do nothing and continue with installation?
Edited by: Citizen_2 on Nov 14, 2010 1:02 AM

Thank you Srikanth. I invoked asmca. Both ASM instances are up.
Under ASM instances Tab
Status ====> 'UP' for both nodes
ADVM Driver status ====> 'Loaded' for both
Under Disk groups tab
Disk group for OCR and VOTE's status is 'MOUNTED (2 Of 2)'
Disk group for Datafiles' status is 'MOUNTED (1 of 2)'
I cliked 'Mount All' button. But got the error
ORA-15017: diskgroup "DG1" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DG1"
CRS-2674: Start of ora.DG1.dg on node2name failedNode2 recognizes OCR Disk group though. But it doesn't recognise the Disk group DG1 created for Datafiles
- fROM NODE2
$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.2.0 Production on Tue Nov 16 15:27:19 2010
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options
SQL> startup
ORA-00099: warning: no parameter file specified for ASM instance
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> ALTER DISKGROUP DG1 MOUNT;
ALTER DISKGROUP DG1 MOUNT
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15017: diskgroup "DG1" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DG1"
--- But OCR is recognized
SQL> ALTER DISKGROUP ALL MOUNT;
ALTER DISKGROUP ALL MOUNT
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15017: diskgroup "DG_OCR_VOTE" cannot be mounted
ORA-15013: diskgroup "DG_OCR_VOTE" is already mounted

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.

Raw devices problem

Hello, I made a model on Vmware ESX for testing Oracle RAC, so it's two Centos 5.10 machines with shared disks. I'm using raw devices for ocr, voting disks and data, and without ASMLib library.
After installing clusterware and Oracle (10gR2), everything was OK until now, when after reboot of one node, no more shared disks exist anymore. For every raw disk related comand I got an error:
#raw -qa
Cannot open raw device '/dev/rawctl' (No such file or directory)
#service rawdevices restart
Assigning raw devices:
/dev/raw/raw1 --> /dev/sdb1
Cannot open raw device '/dev/rawctl' (No such file or directory)
Didn't find anything related to this in /var/log's. Could be glad if someone could explain how to fix it.

Yes, but keep in mind that the device tree is not only rebuild after a system restart, but also the order of devices can be different, so for instance /dev/sdc1 may not be the same after a system restart if you attach or remove another device or plug in any USB. That's why UDEV should be configured to use the unique device identifier to map storage devices which require persistent device naming.
For instance you could use the following entry to map e.g. current /dev/sdc1 to /dev/vote1
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="361a98001686f6959614a453133524171", NAME="vote1", OWNER="oracle", GROUP="oinstall", MODE="0640"
Using raw devices is no longer necessary, not for Oracle, which uses the O_DIRECT flag when opening a device and it does not matter if it is a device or partition. But if you really want to map to raw device names, you could use the following:
ACTION=="add", KERNEL=="sd*", PROGRAM=="/sbin/scsi_id", RESULT=="361a98001686f6959614a453133524171", RUN+="/bin/raw /dev/raw/raw1 %N"

Which Raw Device is associated with which disk group.

How do i know, which raw device is associated with which disk group.
select name, header_status, path from v$asm_disk;
NAME     HEADER_STATUS PATH
PROD_DATA1_0000     UNKNOWN     /asmdisk/disk1
PROD_DATA1_0001     UNKNOWN     /asmdisk/disk2
PROD_FLASH1_0000 UNKNOWN     /asmdisk/disk3
PROD_FLASH1_0001 UNKNOWN     /asmdisk/disk4
I mean raw device name is associated with /asmdisk/disk1 ?
Thanks
-Prasad

I am not sure, but it makes me to believe that /asmdisk/disk*s are not really associated with any specific partition on a hard disk but they are merely some type of pseudo partitions or image files created on your / file system. In linux world, you create pseudo partitions/disk image files using losetup command/utility...I am suspecting that these devices are created on your server using similar utility.

ASMlib raw device mapping

We're using ASMlib here, and I'm trying to figure out which raw devices were mapped to which ASM disks. From the installation instructions, our disks must have been created using the "/etc/init.d/oracleasm createdisk VOL1 /dev/sdg1
" command mentioned on Oracle's main site. However the commands to query disks don't seem to provide that link.
For instance the following command:
/etc/init.d/oracleasm querydisk /dev/sdg1
Will tell you if that device is indeed and ASM disk, but it won't tell you which label it maps to. Similarly
/etc/init.d/oracleasm querydisk VOL1
will tell you that the disk with that label is an ASM disk, but won't tell you which raw device it maps to. The reason I'm asking about this is myself and the sysadmins are trying to map our ASM disks back to the raw devices and from there back to the luns. This obviously wasn't documented at the time the disks were created, long before I started working at my current company. We can go from databases to disk groups and from disk groups to ASM devices, but we can't get from ASM device labels to the raw device names which would allow us to go backwards to the luns.
Thanks!

me too...
#/etc/init.d/oracleasm querydisk /dev/sdc5
Disk "/dev/sdc5" is marked an ASM disk with the label "VOL1"
I still find device name from major and minor:
#/etc/init.d/oracleasm querydisk VOL1
Disk "VOL1" is a valid ASM disk on device \[8, 37\]
#ls -l /dev/* | grep 8, | grep 37
brw-rw---- 1 root disk 8, 37 Jul 31 17:48 /dev/sdc5
Script:
#!/bin/sh
if \[ $# -ne 1 \]
then
echo "Please Check arguments."
echo
echo "./getasmlib \[label\]"
echo
echo " ./getasmlib VOL01"
exit 0
fi
LABEL=$1
C=`/etc/init.d/oracleasm querydisk ${LABEL} |grep valid |wc -l`
if \[ ${C} -eq 0 \]
then
echo "Don't Found ${LABEL} Disk in ASMLIB"
exit 0
fi
M=`/etc/init.d/oracleasm querydisk ${LABEL} | awk -F [ '{print $2 }' | awk '{print $1}'`
N=`/etc/init.d/oracleasm querydisk ${LABEL} | awk -F , '{print $2 }' | awk -F ] '{print $1}'`
for x in ` ls -l /dev/* | grep ${M} | grep ${N} | awk '{print $10}' `
do
/etc/init.d/oracleasm querydisk $x |grep ${LABEL}
done
# ./getasmlib VOL1
Disk "/dev/sdc5" is marked an ASM disk with the label "VOL1"
Good Luck

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

Solaris RAW device

Hi,
I'm new on solaris and i want to create raw device, how can i do it?
Thank You

Hi,
To Configuring Raw Partitions or Raw Logical Volumes on Solaris environment
see this link
http://download.oracle.com/docs/html/B10766_08/presolaris.htm#BABJCHDJ :)

ISCSI and Solaris device names ..... target binding settings

Hi,
I configured an iSCSI environment with Sparc Solaris 10 U4 software inititator and EMC CLARiiON CX3-10c.
So far it is working, but I`m wondering about the Solaris device names /dev/rdsk/c5t3d0. I disabled MPxIO
in /kernel/drv/iscsi.conf. I have 32 LUN configured in CX3-10c target. The Host LUNs are 0 ...31, but Solaris
created device nodes started with target 3, e.g. c5t3d0s2 (see output from iscsiadm list target).
# iscsiadm list target -S iqn.1992-04.com.emc:cx.hk193001030.a1
Target: iqn.1992-04.com.emc:cx.hk193001030.a1
Alias: 1030.a1
TPGT: 2
ISID: 4000002a0000
Connections: 1
LUN: 31
Vendor: DGC
Product: RAID 10
OS Device Name: */dev/rdsk/c5t34d0s2*
LUN: 30
Vendor: DGC
Product: RAID 10
OS Device Name: */dev/rdsk/c5t33d0s2*
LUN: 1
Vendor: DGC
Product: RAID 5
OS Device Name: */dev/rdsk/c5t4d0s2*
LUN: 0
Vendor: DGC
Product: RAID 5
OS Device Name: */dev/rdsk/c5t3d0s2*
Why are the device node names stared with target 3 instead of target 0 ????
Thanks for your help !!!
Edited by: test111 on Mar 25, 2008 8:36 AM

Hi,
I configured an iSCSI environment with Sparc Solaris 10 U4 software inititator and EMC CLARiiON CX3-10c.
So far it is working, but I`m wondering about the Solaris device names /dev/rdsk/c5t3d0. I disabled MPxIO
in /kernel/drv/iscsi.conf. I have 32 LUN configured in CX3-10c target. The Host LUNs are 0 ...31, but Solaris
created device nodes started with target 3, e.g. c5t3d0s2 (see output from iscsiadm list target).
# iscsiadm list target -S iqn.1992-04.com.emc:cx.hk193001030.a1
Target: iqn.1992-04.com.emc:cx.hk193001030.a1
Alias: 1030.a1
TPGT: 2
ISID: 4000002a0000
Connections: 1
LUN: 31
Vendor: DGC
Product: RAID 10
OS Device Name: */dev/rdsk/c5t34d0s2*
LUN: 30
Vendor: DGC
Product: RAID 10
OS Device Name: */dev/rdsk/c5t33d0s2*
LUN: 1
Vendor: DGC
Product: RAID 5
OS Device Name: */dev/rdsk/c5t4d0s2*
LUN: 0
Vendor: DGC
Product: RAID 5
OS Device Name: */dev/rdsk/c5t3d0s2*
Why are the device node names stared with target 3 instead of target 0 ????
Thanks for your help !!!
Edited by: test111 on Mar 25, 2008 8:36 AM

AEBS, device name, and Time Machine backups, question

Will changing the device name of my AEBS (what shows up, for example, in a Finder window sidebar, affect time machine backups that live on a an AirDisk? I just want to make sure, before I make any changes, that my computers won't 'lose' the existing backups if I do change the device name.

I'm afraid to try it, but that is what I am not clear about. The Drive name isn't changing, just the AEBS device name. The big question is does TM just care about the drive name, or does it also care about the AEBS device name. If you are right, than I am out of luck. But would love someone to definitely confirm.

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

How to get the ASM to OS device name mapping

Hi all,
This seems to be an often answered question, but usually the answers specify what to do on the OS (e.g. run oracleasm etc) and/or in the ASM database running on the ASM Host (select * from V$...).
In our situation have plug-ins collecting data from Agents. Plugins collect data from Oracle db/ASM targets and from storage arrays.
Back on the OMS we want to be able to report on the ASM to OS device name mapping. To report, we use either the default metadata UI (i.e. data from the sysman.mgmt_emx_... tables) or we have a BI Publisher report that queries the OEM Repository Database (and can join the ECM tables from the different plug-ins).
The link between the ASM path and the OS device name does not seem to be collected by either the Oracle DB/ASM plug-in, nor by any other plug-in (Host/Storage/...).
It would be easy to go to Linux and run a few commands, but we need to support multiple platforms, like AIX, Solaris x86, Windows as well.
A complicating factor is that ASM can be installed in different configurations, e.g. using ASMlib or using udev...
I really suspect this wheel has been invented before?! Or is it really a matter of having multiple OS-specific low-level scripts and adding a bunch of instance parameters for allowing the user to specify all OS-specific path/utility names etc?
Any suggestions welcome... :-)
Many thanks,
Ed

Google is your best friend ;-)
Those are standard CGI variables, must be available in PHP/ASP(X)/JSP/your-favorite.
Anyway, try this:
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.util.*;
/** Creates a table showing the values of all the CGI variables.
* Part of tutorial on servlets and JSP that appears at * http://www.apl.jhu.edu/~hall/java/Servlet-Tutorial/ * 1999 Marty Hall; may be freely used or adapted. */ public class ShowCGIVariables extends HttpServlet { public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { response.setContentType("text/html"); PrintWriter out = response.getWriter(); String[][] variables = { { "AUTH_TYPE", request.getAuthType() }, { "CONTENT_LENGTH", String.valueOf(request.getContentLength()) }, { "CONTENT_TYPE", request.getContentType() }, { "DOCUMENT_ROOT", getServletContext().getRealPath("/") }, { "PATH_INFO", request.getPathInfo() }, { "PATH_TRANSLATED", request.getPathTranslated() }, { "QUERY_STRING", request.getQueryString() }, { "REMOTE_ADDR", request.getRemoteAddr() }, { "REMOTE_HOST", request.getRemoteHost() }, { "REMOTE_USER", request.getRemoteUser() }, { "REQUEST_METHOD", request.getMethod() }, { "SCRIPT_NAME", request.getServletPath() }, { "SERVER_NAME", request.getServerName() }, { "SERVER_PORT", String.valueOf(request.getServerPort()) }, { "SERVER_PROTOCOL", request.getProtocol() }, { "SERVER_SOFTWARE", getServletContext().getServerInfo() } }; String title = "Servlet Example: Showing CGI Variables"; out.println(ServletUtilities.headWithTitle(title) + "\n" + "
" + title + "\n" + "\n" + "\n" + "CGI Variable Name
Value"); for(int i=0; iNot specified"; out.println("
" + varName + "
" + varValue); } out.println("
"); } public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { doGet(request, response); } }

ISCSI device mapping on Solaris 10

Hi,
A brief overview of my situation:
I have 3 Oracle Solaris X86-64 virtual machines that I'm using for testing. I have configured a ZFS storage pool on one of them (named solastorage), that will serve as my iSCSI target. The remaining 2 servers (solarac1 and solarac2) are meant to be my RAC nodes for a test Oracle 11g R2 RAC installation.
/etc/hosts listing:
# ZFS iSCSI target
192.168.247.150 solastorage solastorage.domain.com
# RAC Public IPs
192.168.247.131 solarac1 solarac1.domain.com loghost
192.168.247.132 solarac2 solarac2.domain.com
A brief overview of the steps carried out at solastorage (after enabling the iSCSI target service):
zpool create rac_volume mirror c0d1 c1d1
zfs create -V 0.5g rac_volume/ocr
zfs create -V 0.5g rac_volume/voting
zfs set shareiscsi=on rac_volume/ocr
zfs set shareiscsi=on rac_volume/voting
On both the RAC servers (of course I've enabled the iSCSI initiator service on both):
iscsiadm modify discovery -t enable
iscsiadm add discovery-address 192.168.247.150
devfsadm -i iscsi
After that, when I run format on both sides, I can see the following:
solarac1# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63>
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c3t15d0 <DEFAULT cyl 509 alt 2 hd 64 sec 32>
/iscsi/[email protected]%3A02%3A54d1d1d2-7154-ee78-94e6-c3d053ca7ab50001,0
2. c3t16d0 <DEFAULT cyl 2045 alt 2 hd 128 sec 32>
/iscsi/[email protected]%3A02%3Af109f049-9f76-6a16-c36a-d42c4d6818fe0001,0
solarac2# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63>
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c2t2d0 <DEFAULT cyl 509 alt 2 hd 64 sec 32>
/iscsi/[email protected]%3A02%3A54d1d1d2-7154-ee78-94e6-c3d053ca7ab50001,0
2. c2t3d0 <DEFAULT cyl 2045 alt 2 hd 128 sec 32>
/iscsi/[email protected]%3A02%3Af109f049-9f76-6a16-c36a-d42c4d6818fe0001,0
solastorage# iscsitadm list target -v | more
Target: rac_volume/ocr
iSCSI Name: iqn.1986-03.com.sun:02:54d1d1d2-7154-ee78-94e6-c3d053ca7ab5
Alias: rac_volume/ocr
Connections: 2
Initiator:
iSCSI Name: iqn.1986-03.com.sun:01:2a95e0f4ffff.4d586ac7
Alias: solarac1
Initiator:
iSCSI Name: iqn.1986-03.com.sun:01:2a95e0f4ffff.4d5b7cef
Alias: solarac2
ACL list:
TPGT list:
LUN information:
LUN: 0
GUID: 600144f04d5b8fca00000c29655dc000
VID: SUN
PID: SOLARIS
Type: disk
Size: 512M
Backing store: /dev/zvol/rdsk/rac_volume/ocr
Status: online
So, here I can see the same devices on both the servers, only it is being recognised with different device names. Without using any 3rd-party software (for example Oracle Cluster), how can I manually map the device names on both these servers so that they are the same?
Previously, for Oracle 10g Release 2, I was able to use the metainit commands to create a pseudo-name that is the same on both servers. However, as of Oracle 11g R2, devices with the naming format /dev/md/rdsk/.... are no longer valid.
Does anyone know of a way I can manually re-map these devices to the same device names on the OS level, without needing Oracle Cluster or something similar?
Thanks in advance,
NS Selvam
Edited by: NS Selvam on Feb 16, 2011 1:32 AM
Edited by: NS Selvam on Feb 16, 2011 1:33 AM

Thank you for your response.
Setting the "ddi-forceattach" property in Pseudo driver .conf file will not
help. Solaris does not "attach" Pseudo drivers which do not have ".conf"
children (even though the Pseudo driver conf file has "ddi-forceattach=1"
property set). Opening the Pseudo device file will attach the Pseudo driver.I'm confused... We have a .conf file, as mentioned, but what makes
it a "Pseudo driver .conf" rather than just a "driver .conf"?
From what I undestand of your requirement, the following should be sufficient :
1. Set property : "ddi-forceattach=1" for all physical devices that is
required by Pseudo driver.
2. Application opens the Pseudo device node.
Let me know if you have any queries / issues. I do have further questions.
Included below is a version of our .conf file modified to protect the
names of the guilty.
As you can see, there is part of it which defines a pseudo device,
and then a set of properties that apply to all devices. Or that's the
intention.
In #1, you said to set the ddi-forceattach property for all "physical
devices", but how do I do this, if it's not what I'm already doing? And what
do you mean "required by Pseudo driver"?
name="foobar" parent="pseudo" instance=1000 FOOBAR_PSEUDO=1;
ddi-forceattach=1
FOOBAR_SYM1=1
FOOBAR_SYM2=2
FOOBAR_SYM3=3;
On a Solaris 9 system of mine, recently I believe I have seen multiple cases
where I've booted, and a physical device has not gotten attached, but if I
reboot, it will be attached the next time.
Thanks,
Nathan

Configuring Storage for Clusterware on Raw devices

My proposed system is:
- Sun Solaris 10
- Oracle 10G RAC
- Oracle Clusterware
- Raw devices for Clusterware files
- ASM for database flies
Assume I have appropriately sized LUNs assigned on my SAN for OCR and voting disks. My question is, how do I configure the raw devices required for these Clusterware files?
I have read the Oracle RAC/Clusterware installation guide (Sun Solaris, SPARC), which goes as far as identifying the requirements but does not give the procedure. If I wish to use raw devices for ASM, it gives a procedure for creating partitions on the LUNs. Is anything like this required for the Clusterware files (OCR and voting disks)?

As far as I know, Solaris follows the traditional raw device definition, which basically says that a raw device is a disk or a partition on a disk that does not contain a file system (yet). Given your question, this would mean that any device that you can find that does not contain a file system would be a raw device.
Message edited here:
However, you need to find the right link to this device in order to use it as a raw or character device. Otherwise, the device would be used as a block device, which means it will be buffered.
On Solaris, those character devices should be listed under /dev/rdsk, while the block device would be listed under /dev/dsk. (Please, refer to: http://www.idevelopment.info/data/Unix/Solaris/SOLARIS_UnderstandingDiskDeviceFiles.shtml)
End of update.
Therefore, you have 2 options in your case. You can create LUNs in your storage that would be just suitable to host your Voting Disks and OCRs OR you can create a bigger LUN and put an OCR and a Voting Disk on this one, AFTER you have sliced the disk (LUN) using the format command.
There is only one thing to remember: If you follow Oracle's recommendation to use multiple Votings and mirrored OCRs, it would obviously be better that those devices do not all share the same LUN (for availability reasons).
Last but not least, you may want to have a look at the following forum for a similar discussion on using RAW devices under Solaris: http://forum.java.sun.com/thread.jspa?threadID=5073358&messageID=9267900
Hope that helps. Thanks.
Message was edited by:
MarkusM

Raw devices files

Hi,
I already created raw devices on database 10g R2. How can make those raw devices available to oracle user?
Best Regards
Yassin
Message was edited by:
Yassin

Yes, the os is Sun Solaris and my question how can
create tablespaces on raw devices.create tablespace abcd datafile '/dev/rdsk/c0t0d0s4/abcd.dbf' size ...
This is an example only, adapt it to your needs! Never fill up the rawdevice completely, leave some space for emergency situations. A different question: why are you using raw devices? What's the output of uname -a? Beginning with Solaris 8 (don't know the maintenance level), you can mount filesystems with the direct io option which gives you almost raw device performance with all advantages of a file system.
Thank you.
Yassin
Message was edited by:
Yassin

Raw device not seen after reboot the server

hi,
I hv upgrade kernal in linux 7.2 but when reboot system no raw device found
how can find out raw device

From http://www.fors.com/orasupp/unix/37914_1.HTM
Raw Devices and Oracle - 20 Common Questions and Answers
2. How can a raw device be recognised?
In the /dev directory, there are essentially two type of files: block
special and character special. Block special files are used when data is
transferred to or from a device in fixed size amounts (blocks), whereas
character special files are used when data is transferred in varying
size amounts. Raw devices use character special files; a long listing
of the /dev directory shows them with a 'c' at the leftmost position of
the permissions field, e.g.
crw-rw-rw- 1 root system 15, 0 Mar 12 09:45 rfd0
In addition, character special files usually have names beginning with
an 'r', as shown in the above example. Some devices, principally disks,
have both a block special device and a character special device
associated with them; for the floppy diskette shown above, there is also
a device
brw-rw-rw- 1 root system 15, 0 Apr 16 15:42 /dev/fd0
So the presence of a 'c' in a device does NOT necessarily mean this is a
raw device suitable for use by Oracle (or another application).
Generally, a raw device needs to be created and set aside for Oracle (or
whatever application is going to use it) when the UNIX system is set
up - therefore, this needs to be done with close co-operation between
the DBA and UNIX system administrator.
Once a raw device is in use by Oracle, it must be owned by the oracle
account, and may be identified in this way.

Question on raw device names in Solaris

Similar Messages

Maybe you are looking for