cancel
Showing results for 
Search instead for 
Did you mean: 

"cooked files" and Oracle

Stanimir
Trusted Contributor

"cooked files" and Oracle

Could anybody explain me what is
the idea of using "cooked files"
with Oracle? What is "cooked files"
and how this one help for better
performance of DB? How I can use
this technology?
8 REPLIES
Thierry Poels_1
Honored Contributor

Re: "cooked files" and Oracle

Hi,

"cooked files/filesystems" refers to "normal" mounted filesystems. So Oracle datafiles are placed in directories, just like other files.

The other option is to use raw file systems, where a full logical volume is used as one Oracle datafile.

"Cooked filesystems" are easier to manage at a small performance cost.

regards,
Thierry.
All unix flavours are exactly the same . . . . . . . . . . for end users anyway.
Graham Cameron_1
Honored Contributor

Re: "cooked files" and Oracle

This one comes up quite often.
Here's a recent thread...

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=234347

-- Graham
Computers make it easier to do a lot of things, but most of the things they make it easier to do don't need to be done.
Stanimir
Trusted Contributor

Re: "cooked files" and Oracle

Thanks for answers!
But my question is more about
how I can configure Oracle DB to use
"cooked files" /step by step,if posible/.
Any real experiece?
Any good documents about it?
Hari Kumar
Trusted Contributor

Re: "cooked files" and Oracle

Hope you are aware of mounting normal filesystems,
When creating creating oracle tablespaces, you will be creating the datafiles, which inturn will be using the space in the mounted file systems and there is no seperate creation techniques for the cooked filesystems for oracle.cooked the name itself sounds its meaning, where for RAW we have lots of procedure for handling.
Create tablespace( datafile) whose path using the filesystems( A very Normal CREATE TABLESPACE command.....)

Information is Wealth ; Knowledge is Power
Yogeeraj_1
Honored Contributor

Re: "cooked files" and Oracle

hi,
-
"Cooked" Datafiles are directly related to tablespaces. hence, if you want to use "cooked" datafiles (which in fact would be same when using raw), you would create your tablespace as:
-
create tablespace tbs_medium
datafile '/u03/oracle/datafiles/tbs_medium_01.dbf'
size 25m reuse
autoextend on
maxsize 100m
extent management local uniform size 1m;
-
The above SQL statement will create a locally managed tablespace which will also be the way to go. Also, the "cooked" file will be automatically created if you have enough space on the /u03/ file system.
-
hOpe this helps
regards
Yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Steven E. Protter
Exalted Contributor

Re: "cooked files" and Oracle

Cooked: regular filesystem

Raw: supposedly faster, but no OS commands to copy and manipulate files. This scares some DBA's.

Someone came up with cooked as a name opposite to raw. Comediens. I've been working with raw logical volume databases since 1996. Its not so bad so long as you are sharp on your utilities(sqlplus).

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com

Re: "cooked files" and Oracle

Because cooked files are just files sitting on filesystems it is easier to delete them by excident. It is more probable than excidently using vgremove to remove a LVM's "raw" logical volume. It's one more reason why I prefer using LVM for oracle.

Just my five cents...
Regards,
Marcin

Re: "cooked files" and Oracle

Of course I meant lvremove not vgremove :-)

Marcin