Convert Raw Device to file system based file systems for datafiles [HP-UX]

Hello experts,
Once again in seek of guidance..
I am in the process of migrating my database (Oracle 7.2.3 on HP-UX 10.20 to Oracle 8.1.7 64-bits on HP-UX 11).
Amongst one of our steps is to convert our RAW Device datafiles to File System based files within the same server and version - Oracle 7.2.3 on HP-UX 10.20.
E.g. /dev/vg00/rlvol1 to become /d01/oradata/cmtdb/tbs1.dbf
Is this something possible?
Can i just do the following:
a. Shutdown database (normal)
b. dd if=/dev/vg00/rlvol1 of=/d01/oradata/cmtdb/tbs1.dbf bs=20k
c. chown oracle7:dba /d01/oradata/cmtdb/tbs1.dbf
d. svrmgrl> startup mount
e. alter database rename file '/dev/vg00/rlvol1' to '/d01/oradata/cmtdb/tbs1.dbf'
f. alter database open.
Thanks very much for your replies.
Please tell me about possible problems that i can anticipate.
Best Regards
Yogeeraj

Similar Messages

Urgent : OS Block header size (convert raw device to filesystem using dd)

Hi,
We need to convert oracle datafiles raw devices to filesystem.
Environment: Oracle 8.1.7 on solaris 8.
Our unix team is unable to tell the value of os block header size to be used for skip/iseek parameter of "dd" command. I know that rman "copy datafile" can be used but it does not help for converting redo log files.
could someone please help.
Thanks.
Rakesh

DB has been shutdown, cold backups have been taken and cannot make any changes at this point.
Is it so tough to know this value ?
Just to clarify, in the following dd command, what should be the value of skip :
dd if=/dev/rdsk/rawfile1of=/data/file1 bs=8192 skip=??? count=100000
Thanks,
Rakesh

Grainy when elements converts raw to psd file in editor.

Hello,
Im having trouble with elements 11. I bring a file in from lightroom and convert it to pds (though i have tried tiff too). Whenever i get it into elements editor, its REALLY grainy and not sharp at all. The image on the left (is in editor) the right is lightroom. Also, if i bring a raw file into the raw file editor of elements, its just fine, but the second i "open" it in editor as a psd, the quality turns horrible. Help!

System info? Versions? Exact settings? PS only opening the merged view could indicate that the file contains data unique to Elements which it cannot interpret.
Mylenium

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 to JPG file conversions too small?

Hello,
I recently upgraded to CS3 from CS so I'm now using Bridge/ACR to convert my RAW files to .JPGs. What is puzzling me is, if I open one or more RAW files in Bridge, make some adjustments (usually WB, exposure, etc.), then use the Save Image option within Bridge to save the image(s) as .JPGs, I am getting very small file sizes (I'm using the Max Quality setting in Bridge, which is 10). For example, a RAW file goes from 6.5MB to 1.2MB. However, if I open the RAW file in Photoshop instead of Bridge/ACR, make adjustments, then save as a maximum quality .jpg, the file goes from 6.5MB to 4.5MB. My concern is that when using the batch/save option within Bridge I'm losing quality somewhere?
Any ideas?
Thanks,
FTP

Hi Omke,
Thank you for sharing your workflow--very generous and quite interesting.
Yesterday, I barged into an Adobe Forums thread similar to mine and I discovered the reason for the file size difference, it's the 10 setting you get when you select Maximum Quality from the Bridge Save Image dialogue box. Bridge, like PS, actually goes to a 12 quality setting, but you have to type in the 12 manually (a curious requirement) rather than selecting the Max Quality option, which always goes to 10. Once I manually typed in 12, my Bridge-converted (RAW to .jpg) files became precisely the same size as when I convert them using PS.
Here's a link to the thread:
charles badland, "raw to jpeg,jpeg file too small" #36, 30 Sep 2008 1:47 pm
Thanks again for your help and suggestions,
--FTP

Device type file compatability with different SAP versions

Hi All,
         I need to know whether there is any difference in Device type file (.PRI) for different SAP versions [ SAP 4.6b , 4.6c, 4.7, mySAP ERP 2005.,]
         Is there any change in .pri file required when upgrading/degrading SAP versions?
        Pls let me know abt this. very urgent..

i tried the following code on a WAS 7.00 SP14 and it works as expected.
create object cached_response type cl_http_response exporting
add_c_msg = 1.
    cached_response->set_data( file_content ).
    cached_response->set_header_field( name =
if_http_header_fields=>content_type
                                       value = file_mime_type ).
    cached_response->set_status( code = 200 reason = 'OK' ).
    cached_response->server_cache_expire_rel( expires_rel = 180 ).
    call function 'GUID_CREATE'
      importing
        ev_guid_32 = guid.
    concatenate runtime->application_url '/' guid into display_url.
    cl_http_server=>server_cache_upload( url      = display_url
                                         response = cached_response ).
call method runtime->server->response->redirect( url = display_url ).
navigation->response_complete( ).

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.

ASM support BLOCK raw device?

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

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

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 devices versus Cluster File Systems in RAC 10gR2

Hi,
Does anyone using cluster file systems in a RAC 10gR2 installation, specifically IBMs GPFS?
Ive 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 RAW DEVICES SUPPORTED OVER A CLUSTER FILE SYSTEM

Can raw partions be defined for datafiles after having choosen Cluster file system as storage option for database while creating fresh database using
DBCA?

> Do update on how the partitions have to be defined in either cases?
For both ASM and OCFS, a partition must exist on the disk - it can be of any partition type. Does not matter. Simply that the s/w references a partition and not an entire disk.
So for example, /dev/sdaf and dev/sdag are two shared devices on the cluster (LUNs on the SAN or whatever).
You create a partition on each. E.g
# fdisk -l /dev/sdaf
Disk /dev/sdaf: 36.5 GB, 36573020160 bytes
255 heads, 63 sectors/track, 4446 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdaf1 1 4446 35712463+ 83 LinuxTo use the first device as a OCFS device, you need to build an ocfs file system on it using mkfs.
And then it can be mounted as a "normal" cooked file system mount. Remember that /etc/fstab needs to be updated for mounting it on startup.
To use the second device for ASM, you have two choices. If you have the ASMlib kernel module installed, you can use that to configure a volume label and assign it for use by ASM.
Alternatively, you simply map the device (partition) to a raw device for detection by ASM. E.g.
# raw /dev/raw/raw1 /dev/sdag1Of course, you also need to make this permanent by updating the raw device list config file so that this mapping is performed on reboot. On Linux, this is the /etc/sysconfig/rawdevices file. Also remember that the user and group access for the logical raw device created, must allow ASM full access to it (e.g. use chmod oracle.dba /dev/raw/raw1).
In a nutshell, this is how to raw devices are used as ocfs and asm volumes. (on RHEL specifically, but I expect no major differences in this approach on other o/s's)

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

Raw Device Backup to file system(OPS 8i)

Hi
Our currently setup is
Oracle database 8.1.6 (Oracle Parallel Server) Two Node
Noarchive Mode
Solaris 2.6
all database file ,redo logfiles,controlfiles under raw device.
database size 16 G.B
oracle block size 8192
currently we are using only export backup of oracle.
But now i want to take cold backup of oracle database to disk.
cold backup Raw --> Disk
How we can take cold backup with dd command and skip parameter ?
Is anybody have practical idea of dd command with skip parameter.
Thanks and regards
Kuljeet pal singh

you can use ufsdump instead of dd

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

Need a plugin to convert Raw files with CS 6 standalone version. 8.7.1 version of ACR is not compatible with CS 6 in non-cloud form.

We have a site license for CS6 for our company and for the past year have not been able to convert RAW files from our newer cameras using Adobe Camera Raw. We do not want to use the Cloud version as we work off laptops in the field and overseas and even our offices have only dial-up for internet access where we are located in Monterey.
Can anyone recommend a plugin raw converter so we can continue to batch process our files with CS 6?

The camera raw 8.7.1 plugin should work fine in the photoshop cs6 non cloud license version.
The only exceptions being if you have mac os x 10.6.8 or windows xp/vista, then 8.3 is the newest camera raw plugin that works.
Which operating system(s) do you have?
Have you tried Help>Updates from within photoshop cs6 to get the 8.7.1 camera raw plugin.
Here's an 8.7.1 camera raw plugin installer for photoshop cs6
https://helpx.adobe.com/x-productkb/multi/camera-raw-plug-in-installer.html

Convert Raw Device to file system based file systems for datafiles [HP-UX]

Similar Messages

Maybe you are looking for