Oracle raw device conversion on alpha unix

I would like to convert an Oracle database version 7.3.4 from filesystem to raw devices in digital alpha o/s version 4.0d. Anyone knows how to do it (i.e., can I simply use dd to convert? do I need to include 'skip' and 'seek' in dd command?)
thanks very much

Each raw device you create is used as a single data file.
Eg mklv -y 'myfile' <vgname> <number of logical partitians>
Will have two special files associated with them /dev/rmyfile and /dev/myfile. The number of logical partitians will be the size of your datafile subtract 1 meg for overhead.
So, if you were addding the above raw volume to a tablespace, and the lp size was 32 meg, you would
create tabelspace tsname datafile '/dev/rmyfile' size 31 m;
Note the use of rmyfile not myfile.

Similar Messages

Managing DB on Raw Devices

I am wondering what's the difference to configure/manage DBs on raw devices? Looking for some good articles/study material....

Hi Arif,
what's the difference to configure/manage DBs on raw devices? Not many people use "plain" raw anymore, it's all about managing the pp entries. In many UNIX environments, raw devices are called virtual storage devices (VSDs). These VSDs are created from disk physical partitions (PPs), such that a single VSD can contain pieces from several physical disks. It is the job of the system administrator to create a pool of VSDs for the Oracle administrator. The Oracle administrator can then take these VSDs and combine them into Oracle datafiles. This creates a situation where an Oracle datafile may be made from several VSDs. This many-to-many relationship between Oracle datafiles and VSDs makes Oracle administration more challenging.
Do you have a relrease of Oracle that supports ASM? ASM allows raw, plus file management.
Looking for some good articles/study material.... OK, look for tips on:
Direct I/O:
http://www.google.com/search?&q=oracle+direct+i%2fo
Oracle Raw device partitions:
http://www.google.com/search?&q=oracle+raw+partitions+
Oracle ASM:
http://www.dba-oracle.com/art_so_disk_tuning_1.htm
Hope this helps. . . .
Donald K. Burleson
Oracle Press author

RAW DEVICE와 FILE SYSTEM 간에 오라클 데이터화일 이동하기

제품 : ORACLE SERVER
작성날짜 : 1999-11-30
RAW DEVICE와 FILE SYSTEM 간에 오라클 데이터화일 이동하기
======================================================
유닉스 명령이 dd를 이용하여 오라클 데이터화일을 Unix File System과 Raw
Device 간에 이동할 수 있으나, 플랫폼 별 Raw Device의 특성으로 인하여 주의할
점이 있다. 만일 잘못된 이동으로 인하여 데이터베이스가 기동하지 못하면,
ORA-7366 (sfifi: invalid file, file does not have valid header block.)
에러가 발생할 수 있다.
예를 들어 Digital unix의 경우는 raw device에 64k OS 헤더가 필요하므로 dd
명령어 옵션 중 iseek와 oseek를 활용하여야 한다.
다음은 예제를 통하여 데이터화일을 Raw Device에서 Unix File System으로
이동하는 절차이다.
(운영 현황)
- 현재의 위치: /dev/rdsk/c0t15d0s7
- 이동할 위치: /oracle/file/system.dbf
- 화일의 크기: 488636416 bytes <--- V$DATAFILE.BYTES column 값!
- DB_BLOCK_SIZE: 2048 bytes
(준비 단계)
1. Oracle 블럭 수 계산:
BYTES / DB_BLOCK_SIZE = 488636416 / 2048 = 238592 (블럭)
2. O/S file header 블럭 추가:
238592 + 1 = 238593 (블럭)
: "ls -l /oracle/file/system.dbf" 명령으로 확인 가능하며, O/S file
header는 1블럭으로 항상 일정함.
3. Raw Device OS header 블럭 계산:
64K / DB_BLOCK_SIZE = 65536 / 2048 = 32 (블럭)
: 사용할 dd 명령어 중 블럭의 크기를 DB_BLOCK_SIZE(2048바이트)로 할
예정이므로 2048로 나누어야 함.
(명령어 형식)
$ dd if=<raw device> of=<UFS file> bs=<oracle blocksize>
iseek=<blocks to skip> count=<total count>
(명령어 수행 절차)
(1) SVRMGR> STARTUP MOUNT
(2) SVRMGR> !dd if=/dev/rdsk/c0t15d0s7 of=/oracle/file/system.dbf
bs=2048 iseek=32 count=238593
(3) SVRMGR> ALTER DATABASE RENAME FILE '/dev/rdsk/c0t15d0s7' TO
'/oracle/file/system.dbf';
(4) SVRMGR> ALTER DATABASE OPEN;
========================================================================
반대로 Unix File System에서 Raw Device로 이동하는 명령어 형식은 아래와 같다.
(명령어 형식)
$ dd if=<UFS file> of=<raw device> bs=<oracle blocksize> \
oseek=<blocks to skip> count=<total count>
유사한 방식으로 데이타 화일 뿐 아니라 리두 로그 화일도 이동할 수 있다.
[주의] Raw Device의 블럭 헤더의 크기는 OS마다 다를 수 있으므로 플랫폼
벤더사에 미리 확인한 후 작업하여야 한다.

Raw device for red hat

Hi,
I tried to install raw device on red hat 4.2.I posted the mount point of that machine
]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
145G 9.6G 128G 7% /
/dev/sda1 99M 13M 82M 14% /boot
none 2.0G 0 2.0G 0% /dev/shm
/dev/sdb1 459G 350G 86G 81% */ydev*
is it possible to use /ydev for the RAW mount point *.If it's,is it afffect any existing applications at dev?*
please help me out that

All that is required from a system level are partitioned disks. Oracle will handle the configuration of the filesystem. Here are my steps to configure raw devices using LUNs:
--- PARTITION THE RAW VOLUMES ---
fdisk /dev/<disk>
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-512, default 1):<enter>
Using default value 1
Last cylinder or size or sizeM or +sizeK (1-512, default 512): >
Using default value 512
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
--- BIND PARTITIONS TO RAW DEVICES ---
Edit /etc/udev/rules.d/60-raw.rules and add:
# Define mapping of SCSI hard disks for Oracle Raw Devices
ACTION=="add", KERNEL=="sdg1", RUN+="/bin/raw /dev/raw/raw1 %N"
ACTION=="add", KERNEL=="sdj1", RUN+="/bin/raw /dev/raw/raw2 %N"
ACTION=="add", KERNEL=="sdk1", RUN+="/bin/raw /dev/raw/raw3 %N"
# Define persistent raw device permissions
ACTION=="add", KERNEL=="raw*", OWNER=="oracle", GROUP=="dba", MODE=="0660"
--- CREATE THE RAW DEVICES ---
/sbin/start_udev
--- VERIFY RAW DEVICES ---
raw -qa
2. Update permissions of new devices
chown -R oracle:dba /dev/<disks>
3. Create links to device on /dev/oracle
# DETERMINE SCSI LINKS TO DEVICES
clear ; ls -la /dev/disk/by-id/ | grep sd[f-v]1 | awk '{print $11,$9}'| sort
# CREATE VOLUME MEMBER SYMBOLIC LINKS. DONE!

Raw device for oracle 8.1.7 on AIX 4.3.3

Hi there,
I am trying to use a raw device on AIX 4.3.3 for ORACLE 8.1.7.
I have created a raw device /dev/or_system
brw-rw---- 1 oracle dba 54, 1 Mar 04 10:44 or_system
but it is not possible to create a datafile on it :
SVRMGR> create database "GLM"
maxinstances 8
character set "WE8ISO8859P1"
datafile '/dev/or_system' size 150M REUSE
logfile
GROUP 1 ('/oracle/GLM/redo/log1.ora') size 100M,
GROUP 2 ('/oracle/GLM/redo/log2.ora') size 100M,
GROUP 3 ('/oracle/GLM/redo/log3.ora') size 100M,
GROUP 4 ('/oracle/GLM/redo/log4.ora') size 100M;
create database "GLM"
ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '?/rdbms/admin/sql.bsq' near line 407
ORA-00604: error occurred at recursive SQL level 1
ORA-01119: error in creating database file '/dev/or_system'
ORA-27038: skgfrcre: file exists
SVRMGR>
The ORA-27028 in exact this situation was reported as a bug in prior ORACLE Versions 8.0.4/ 8.0.5 and had
the bug no. 690228.
But we use as mentioned 8.1.7.
What do I do wrong?
Any suggestions are welcome.
Thank you
Gerhard

Each raw device you create is used as a single data file.
Eg mklv -y 'myfile' <vgname> <number of logical partitians>
Will have two special files associated with them /dev/rmyfile and /dev/myfile. The number of logical partitians will be the size of your datafile subtract 1 meg for overhead.
So, if you were addding the above raw volume to a tablespace, and the lp size was 32 meg, you would
create tabelspace tsname datafile '/dev/rmyfile' size 31 m;
Note the use of rmyfile not myfile.

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

Create raw devices for OCR & Voting Disk for Oracle 10g R2 RACLinux 64 bit)

Hi Friends,
Please let me know the Document to cretae RAW Disk for OCR and Voting Disks (like rpm's required,process tio cretae raw disks) in Oracle 10g R2 on Linux (64 bit)
Regards,
DB

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]

Why don't we keep Oracle Database ARCH logs in RAW devices

Hi All,
Why don't we keep Oracle Database ARCH logs in RAW devices?
How ARCH process is related to Block Device and Character Device ?
Thanks,
Tusar
Edited by: user11987718 on 26-Jun-2012 09:59

Why don't we keep Oracle Database ARCH logs in RAW devices? 1.This is because raw devices do not enable sequential writing of consecutive archive log files.
http://docs.oracle.com/cd/E11882_01/rac.112/e16795/rman.htm#RACAD320
2.with raw you have to specify the exact size of the file at creation time, in contrast with file system, where you can create file without specifying its size, start writing to it, apending new blocks to it until you are done, and thus creating a file of whatever size it needs to be to hold all information.
http://www.dbasupport.com/forums/archive/index.php/t-16429.html
3.raw file systems are difficult to manage because you cannot run normal os commands on them.(as there is no file systems)
How ARCH process is related to Block Device and Character Device ?A block device would read/write bytes in fixed size blocks, as in disk sectors. Character devices read/write 0 or more bytes, in a stream, such as a TTY or a keyboard.
For more details about what is block and character device type :
http://en.wikipedia.org/wiki/Device_file
And now think, how arch process is related to block and character devices.
Regards
Girish Sharma

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

Oracle ASM installation and raw device options

I am looking to install Oracle ASM on Linux Red Hat AS 4 (ia64) using Oracle 10.2.0.3.
A general question I have regarding prerequisites for ASM using raw devices. It appears there are 2 options for dealing with RAW devices.
1. Use the ASM library driver
or
2. simply bind the devices to raw devices (and then install a new $OH with an ASM instance)
Is there a recommendation from Oracle, industry best practices, expert opinions on which way to go?
If I understand correctly it sounds like option 2 will require an ASM $OH and instance. Is that right or do both option require this?
Can someone provide guidance as to which option I should use, an Oracle whitepaper, a recommendation, instructions or something.
Any help or insight is provided as to which option I should use.
Thank you.
echardrd

OK. Perhaps I am a little condused then. From what I read Oracle ASM recommends the use of RAW devices for ASM storage devices. What I have is a new LUN presented to my database server from the SAN. I assumed that the LUN needs to be mounted in some fashion on the server, but my SA tells me in order to mount it, would require the use of a filesystem. If we put a filesystem(NTFS, ext, etc) on the LUN prior to mounting it, will ASM be able to use it? If ASM can use a device that has a filesystem on it will this add unneccessary overhead (I/O)?
I guess my question is for ASM should I
1. use a RAW partition or a filesystem? Does it matter?
2. Will RAW have better I/O performance?
3. How do i make the LUN presentation from the SAN a usable RAW device to my database server? Any steps or guidance would be helpful since my SA and I can not seem to bridge this gap.
Thanks.

How can i use raw device in oracle 9.2.0.4

can i use "create tablespace XXX datafile '/dev/raw1' ..." to use raw device for tablespace? Or i should use "ln -s /dev/raw1 /oradata/xxx.dbf"?
does raw device as same as "xxx.dbf" is limited 4GB ?
pool english.

hi,
as far as windows NT OS is concerned,,there's a utility (OCOPY) to store ur datafiles on to raw devices,,,but u cant directly access that datafiles for runtime databases,,its just for backup purposes..
umar

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.

Advantage of using RAW devices for storing database

Hi,
Marry Christmas to all.
Oracle 10g version 10.2.0.1.0 (rac)
OS : HP-UX 11i
I am new to this enviornment. We are using raw devices for storig the database.
Please tell what are the advantages for using raw devices for storing the database?
Thanks.

http://www.fors.com/orasupp/unix/37914_1.HTM
The above link explains the raw devices and advantages.

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

Oracle raw device conversion on alpha unix

Similar Messages

Maybe you are looking for