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

Similar Messages

Convert from raw devices to filesystems

Is there a document or technote that describes a best practice approach to converting a database from raw devices to filesystems?
Thanks!

Thank you for your posting - The Member Feedback forum is not monitored by Oracle support or product teams and so Oracle product and technology related questions cannot be answered. However we recommend that you post this thread to the "Database - General" forum.
The URL is: General Database Discussions
Also, please try using OTN's search function.
Thanks - The OTN team

What procedures exist for change raw devices to filesystem?

What procedures exist for change raw devices to filesystem?
I understand that only you can:
- Backup Full (System with raw device) and Restore in System with Filesystem
- Export/Import
Specifically I want to know:
A backup (created in MaxDB 7.5 with DB in Rawdevices) can be restored on another System, with DB in file system??
Someone could give me details of the procedure?
Someone knows another method?
Greetings to all.

> Specifically I want to know:
> A backup (created in MaxDB 7.5 with DB in Rawdevices) can be restored on another System, with DB in file system??
No problem as long as
- the target systems database version is at the same patchlevel (or higher)
- the target database is big enough
- the target system has the same endianess (you can e. g. not import a backup from Windows to HP-UX)
A SAPDB/MaxDB backup has no information about the source filesystem setup, it contains only pages. There has "just" to be enough space to restore them.
Markus

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

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

Converting raw images to jpegs using PSE 11

I have started to capture only RAW images from my Sony NEX 7 camera. However, I wish to be able to send JPEG images to my friends ( prior to RAW editing ). How do I convert/copy my RAW images to JPEGs using PSE 11?
Thanks
Derek

After you're done in camera raw (or in your case, without doing anything, but you'll just get the default conversion, because you MUST convert the files), click the Open button, then save in the format of your choice in the editor. JPEG is an 8 bit format so you will want to either set the raw converter's pulldown menu to 8 bits or you will need to go to Image>Mode> 8 bits/channel in the editor. If you're emailing, you can also use Save for Web to size them down if necesary.
If you use the organizer, you can just use file>export as new files and be sure to send the jpgs someplace easy to find.

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.

Raw device access checking

how i can check that OCR & Voting disk can access raw devices? & how i can check the size of raw devices also?

Once you find the raw devices, see your thread from yesterday on the subject, you can /sbin/fdisk -l <device name> to find information about the size.

SAPINST : Error CJS-00091 with raw devices on AIX 5.2

Dear all,
I am trying to install a Web Application Server Java 6.40 SR1 on AIX/Oracle but get the following error due to the fact that I opted for a raw-device installation.
> CJS-00091 Unable to create the tablespaces.
> DIAGNOSIS: There is not enough free disk space:
>
> Mount point | space required | space available | SAPDATA directories
> /oracle/DEP | 2805 | 933.887 | 1,2,4
>
> SOLUTION: Make more disk space available.
You will probably tell me that an OSS note exists and that I should adapt the 'control.xml' within the installation directory but that's not the point. This problem was probably present in older releases but is now corrected with the Support Release 1 (SR1) of Netweaver '04
In fact, I don't understand why SAPINST still tries to work with the classical "SAPDATA" structure as it should now work with the "SAPRAW" directory only (See OSS Note 145654). This "SAPRAW" directory is only containing links refering to the raw devices SAPINST should use.
Here's what I've got :
> ls -la sapra*
>
> drwxr-xr-x 2 oradep dba 256 15 Feb 11:29 cntrl
> lrwxrwxrwx 1 oradep dba 18 15 Feb 11:28 depdb_1 -> /dev/rdepddb010013
> lrwxrwxrwx 1 oradep dba 18 15 Feb 11:28 depdb_2 -> /dev/rdepddb010014
> lrwxrwxrwx 1 oradep dba 18 15 Feb 11:28 depdb_3 -> /dev/rdepddb010015
> lrwxrwxrwx 1 oradep dba 18 15 Feb 11:28 roll_1 -> /dev/rdepddb010011
> lrwxrwxrwx 1 oradep dba 18 15 Feb 11:28 system_1 -> /dev/rdepddb010009
> lrwxrwxrwx 1 oradep dba 18 15 Feb 11:28 temp_1 -> /dev/rdepddb010010
> lrwxrwxrwx 1 oradep dba 18 15 Feb 11:28 undo_1 -> /dev/rdepddb010012
And here's the "SAPDATA" structure SAPINST wrongly created
> ls -la sapda*
>
> sapdata1:
> drwxr-xr-x 2 oradep dba 256 15 Feb 11:28 system_1
>
> sapdata2:
> drwxr-xr-x 2 oradep dba 256 15 Feb 11:28 roll_1
> drwxr-xr-x 2 oradep dba 256 15 Feb 11:28 temp_1
>
> sapdata4:
> drwxr-xr-x 2 oradep dba 256 15 Feb 11:28 depdb_1
Any idea, what the problem is?
I presume the installation script contains some bugs when working with raw devices but would like to know whether someone already experienced this...
Many thanks for your help,
Xavier Vermaut
SAP BC Administrator
Unisys Belgium

Hello Arun,
Maybe I am wrong but I think you did not understand what was the problem...
When using 'raw devices', SAPINST shouldn't use the classical SAPDATA directory structure but should only create links into the 'SAPRAW' directory.
So, SAPDATA directories should not exist! Only links (refering to the raw devices to be used) within the SAPRAW directory should be present!
In the meantime, I got this problem solved by SAP. They temporarily modified my 'keydb.xml' file to get this fixed but they should release an appropriate correction within a few days. This way of doing (I mean modifying the 'keydb.xml') is only applicable to my system...
Cheers,
Xavier

Raw device size

How can we find the raw device size from OS level?

Thanks Chandra!!
Still I can't see the size of the file.
lsattr -E -l rrawspace68
lsattr: 0514-519 The following device was not found in the customized
device configuration database:
rrawspace68
When I do the following
lsattr -E -l rawspace68 => output is as followed
copies 2 Number of physical partitions e
inter x Policy for allocation over mule
intra m Policy for allocation on physie
label None Information label e
lvserial_id 000c8c900000d60000000120a0521407.68 Volume group identifier . minoe
relocatable y Bad block relocatable policy e
size 40 Number of logical partitions ie
strictness y Copies allocation policy e
stripe_size Stripe Size e
stripe_width 0 Striping Width e
type raw Type description e
upperbound 128 Number of physical volumes to e
How can we figure-it-out the size of the device?
Thanks
Srini

Raw device size checking

How i can check the /dev/raw/raw* size and all information regarding that.

Have you tried /sbin/fdisk -l <device>
raw device permissions
raw device access checking

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.

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

ORA-00354: corrupt redo log block header..urgent

Hi All,
i am running into an issue when trying to recover a datafile.
1). Logs are being applied to the datafile to recover but RMAN is throwing this error:
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver logfile 'H:\ORACLE_ARCHIVE_LOGS\RBS\ARCHIVELOG\2012_04_23\O1_MF_1_13174_7SC4
P56W_.ARC'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 32768 change 6715041179 time 04/23/2012 13:
33:51
ORA-00334: archived log: 'H:\ORACLE_ARCHIVE_LOGS\RBS\ARCHIVELOG\2012_04_23\O1_MF
_1_13174_7SC4P56W_.ARC'
thanks in advance

bcm@bcm-laptop:~$ oerr ora 353
00353, 00000, "log corruption near block %s change %s time %s"
// *Cause: Some type of redo log corruption has been discovered. This error
//          describes the location of the corruption. Accompanying errors
//          describe the type of corruption.
// *Action: Do recovery with a good version of the log or do incomplete
//          recovery up to the indicated change or time.
bcm@bcm-laptop:~$ oerr ora 354
00354, 00000, "corrupt redo log block header"
// *Cause: The block header on the redo block indicated by the accompanying
//          error, is not reasonable.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time. If this happens when archiving,
//          archiving of the problem log can be skipped by clearing the log
//          with the UNARCHIVED option. This must be followed by a backup of
//          every datafile to insure recoverability of the database.

Cold backup of controlfile raw device

We have Oracle 9.2.0.4 on AIX 5L on node 1 and node3 with controlfile as raw device. These two nodes are connected through LAN. I shutdown the database DB on node1 and take the backp of controlfile in /ora/backup on node1 usind dd command. I mput this file in binary mode on node3 over ftp. On node3 when I tried to mount the database using this controlfile it gave error
"ora-0201- controlfile version incompatible with oracle version."
In alert log it showed the message
Corrupt block relative dba: 0x00000001 (file 0, block 1)
Fractured block found during control file header read
Data in bad block -
type: 0 format: 0 rdba: 0x00000000
last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
consistency value in tail: 0x00000000
check value in block header: 0x0, block checksum disabled
spare1: 0x0, spare2: 0x0, spare3: 0x0
What can be the exact problem?? Any hlep.

Why are you mounting or doing this ? I think databases on node1 and node3 are not the same. Controlfile of a database cannot be used to mount a different database.
fyi,
ORA-00201 controlfile version string incompatible with ORACLE version string
Cause: The control file was created by incompatible software.
Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release.

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.

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

Similar Messages

Maybe you are looking for