Raw Device and ASM configuration

Can any body send me steps/commands to configrue Raw device and then ASM on top of it for RAC?

Try this:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14231/storeman.htm#i1021337
And this for installing 10g RAC on RH:
http://www.puschitz.com/InstallingOracle10gRAC.shtml
Daljit Singh

Similar Messages

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.

Oracle database 10g RAC and ASM configuration

Hi all,
I want to ask to everybody something about Oracle 10g RAC and ASm configuration. We plan to migrate to Oracle 10g from 9i, and we will begin configuring oracle but we have to decide which configuration are the best.
Our materials are bellow:
Hardware: RP 3440 (HP)
OS : HPUX 11i Ver 1
Storage: EVA 4000 (eva disk group)
The problem is:
Our supplier recommand us to use HP serviguard + HP serviceguard extension for RAC+ RAc and Raw device as configuration.
But we want to use Oracekl Clusterware + RAC + ASM
My question is if anybody know what is the best configuration, we want to use ASm.
Can we use HP serviguard and ASM.
Some documentations or link explain oracle RAC and ASM configuration will be appreciate.
Thanks for your help.
Regards.
raitsarevo

Hello,
there's no extra RAC software package, but the option is only offered, if one of the supported cluster layers for the respective OS has been installed before.
10.1.0.3 looks like a complete redesign, but anyway it is a patch, you have to install 10.1.0.2 first.

Raw device to ASM

Hi,
How can i move the "RAW device" Migrating to ASM
what are the steps to be followed
Oracle Version : 11.1.0.7.0
Platform: AIX 6.1
Thanks,
Ramesh

Aman.... wrote:
ASMLIB is not mandatory to use the raw device with ASM. Its an "add-on" to improve the performance, that's all!Not really a performance improvement as it cannot make ASM I/O go any faster - it is a more a management driver that enables you to manage ASM disks/LUNs via an ASM command line interface. But as you said, it is not mandatory. I personally prefer using udev and multipath directly on Linux for configuring and maintaining device names and permissions for all disks and LUNs and not treat ASM ones differently via another interface.
Also, as ASMlib is a kernel module, it is another moving part at boot time. It needs to match the kernel version used. It and other similar kernel drives need to "+play nice+" with one another. And this is the primary reason we've stopped using ASMlib after we first tried it with 10.1 RAC. There were incompatibilities between it and a vendor kernel driver, resulting in adhoc ASM I/O errors. And the Metalink Note at the time stated that there are no incompatibilities between ASMlib and such vendors drivers... (and I did request Support to amend that note after the incompatibility was identified via a SR, but it never was).

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

Raw device in ASM

Hi,
I am assigning raw devices to ASM on IBM-AIX 5.2. But the devices are not visible in ASM. Please somebody help me how to identify the disks in ASM or from AIX to check whether the disks are accessiable. I am able to ls -lrt and find the disk. but not able to identify the raw disk size
Thanks for your help

In some OSs raw devices are only visible to root unless the permissions are explicitly reset.
Have you read the appropriate section in the RAC install guide for AIX? (http://download.oracle.com/docs/cd/B19306_01/install.102/b14201/storage.htm#BABHCGIJ)

Difference between raw device and a block device

Platform : Unix, Unix-like
What is the difference between a raw device and a Block device? I found the following URL by googling. But, posts seem to be mutually contradictory
http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1291798907338+28353475&threadId=583811

a raw device is a special kind of block device file that allows accessing a storage device such as a hard drive directly, bypassing the operating system's caches and buffers (although the hardware caches might still be used). Applications like a Database management system(Oracle ) can use raw devices directly, enabling them to manage how data is cached, rather than deferring this task to the operating system.
block devices correspond to devices through which the system moves data in the form of blocks. These device nodes often represent addressable devices such as hard disks, CD-ROM drives, or memory-regions.
Also Check :
http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1291806443666+28353475&threadId=987277
Regards
Rajesh

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.

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

Raw device and Oracle

Hi,
did anybody successfully test Stephen Tweedy3s raw device against
Oracle? I testet also against Sybase but could not get it to run.
Stephen checked straces and stuff but there seems to be no error!
Look at ftp.uk.linux.org/pub/linux/sct/fs
This patch is against Linux 2.2.9.
Please people, test it and tell me if it works for you
Cheers
Marcus
null

Marcus Ruehmann (guest) wrote:
: Hi,
: did anybody successfully test Stephen Tweedy3s raw device
against
: Oracle? I testet also against Sybase but could not get it to
run.
: Stephen checked straces and stuff but there seems to be no
error!
: Look at ftp.uk.linux.org/pub/linux/sct/fs
: This patch is against Linux 2.2.9.
: Please people, test it and tell me if it works for you
: Cheers
: Marcus
Hi Marcis,
I tested raw device with Oracle but in AIX with Oracle 7.3 and
it worked perfectly. While I'm waiting for Oracle8i on Linux and
would test it with raw device, I don't think there would be too
much different.
Brdgs,
Quoc Trung
null

Node is not able to identify new raw device in ASM

Hello experts,
i have a strange probelm with raw disk discovery in ASM. i have a six node cluster. and we are planning to add another raw disk to support database
growth.
out of 6 nodes, 5 nodes are able to find raw disk and on 6th node, it is not able see the disk. not sure what could be the problem.
i have verified the file permissions. i did see 640 and these seems to be correct
My database version : 10.2.0.4
OS RHEL 4.7
here is the info.:
on NOde 5 :
SQL> SELECT name, header_status, path FROM V$ASM_DISK;
NAME HEADER_STATU PATH
MEMBER /dev/raw/raw22
MEMBER /dev/raw/raw21
CANDIDATE */dev/raw/raw23*
FOREIGN /dev/raw/raw5
FOREIGN /dev/raw/raw4
FOREIGN /dev/raw/raw3
FOREIGN /dev/raw/raw2
FOREIGN /dev/raw/raw1
on node 6 :
SQL> SELECT name, header_status, path FROM V$ASM_DISK;
NAME HEADER_STATU PATH
FOREIGN /dev/raw/raw5
FOREIGN /dev/raw/raw4
FOREIGN /dev/raw/raw3
FOREIGN /dev/raw/raw2
FOREIGN /dev/raw/raw1
please guide me..
#! Kumar

The disk attribute reserve_policy may need to be modified for the disk.
Verify if the value of reserve_policy is "single_path"
lsattr -El diskname | grep reserve_policy
if it is, then change it as follows
chdev -l diskname -a reserve_policy=no_reserve
This will ensure the disk is sharable across multiple nodes.

SSD and ASM configurations

Hello all,
Although I realize that the question of configuration on ASM regarding the use of SSD storage devices is, or should be mote at this point.
I still see, from time to time, questions and discussions on this topic in the other forms.
I am wondering if it would be possible to create such a forum just to discuss these questions?
But then where do you put it?
Should this be a storage section for SSD?
Database ASM storage or a subset or either?
What do you think?

smitty8 wrote:
Hello all,
< snip >
But then where do you put it?
No.
If you have an ASM question, post it to the ASM discussion space.
If you happen to have a question dealing with a Sun/Oracle branded piece of storage hardware such as an array or a tape library, it goes here.
You posted today's question to the storage HARDWARE discussion space.
It doesn't belong here.
Edit:
... and because you multi-cross-posted
https://community.oracle.com/thread/3618609
this thread is locked.

How to converrt files on RAW devices in ASM to non ASM file system.

Hi all,
I have on problem .
Is that possible to migrate ASM raw files system to non ASM file .
If possible plzz describe them.
If not also please tell y not?
Thanks in addvance
Regards
Krishna

Hi,
I totally agree with Mahir. And I just want to share one thing:
Use %U to generate guaranteed unique names :
For backupsets, %U means: %u_%p_%c
For an image copy of a datafile, %U means: data-D-%d_id-%I_TS-%N_FNO-%f_%u
For an image copy of an archived redolog, %U means: arch-D_%d-id-%I_S-%e_T-%h_A-%a_%u
For an image copy of a control file, %U means: cf-D_%d-id-%I_%u
Thank you

Raw devices and cluster file system

what is difference between raw and cluster file system

See to this thread if this can help
http://asktom.oracle.com/pls/asktom/f?p=100:11:3285616048047775::::P11_QUESTION_ID:7931107631402

Database Data files on RAW Devices

Hi,
I'm creating a database and wish to locate the tablespaces on a raw device.
How do I specify the datafiles for the tablespaces on the raw device.

> Any reason for moving to raw device?
I actually prefer raw devices and ASM over using cooked file systems.
By default RAW devices eliminate the "interference" of the kernel. It does not manage a file system on the device. There are no other foreign processes that can use that raw device (as is often the case with cooked devices). There is no o/s file system cache for that device. A physical I/O on the Oracle side means a dinkum physical I/O and not a maybe-logical-I/O-from-the-file-system-o/s-cache.
There is no need for me as DBA to manage that file system according to OFA standards (ASM does it for me). There is no need for me to go through the learning curve of using a 3rd party volume manager. I have features like automated load balancing while the instance is up and running.
Yes, there is an argument to be made for just how much of a performance improvement in I/O one can get from a raw device versus a cooked file system. But I/O performance is not the only consideration.

Raw Device and ASM configuration

Similar Messages

Maybe you are looking for