I am not sure how you can copy a regular file which is operating system
dependent to a row file which is managed by Oracle using dd. To me,
your only option may be export/import.
Regards,
Shakir
--- Gene Sais [EMAIL PROTECTED] wrote:
Another option is to shutdown db, backup the files to
the first question is WHY go to raw devices?, OPS/RAC? other than those
2 reasons(and i'm not sure RAC requires it like OPS did), there is very
little performance gain with the advances in filesystem types.
just curious.
joe
Nat wrote:
We are planning to move to raw devices for all our
Dennis,
Thanks for the reply. We have not done any benchmarks to find out if there
is any performance
gain. The main reason for moving to raw devices is to convert our existing
database to function on OPS
environment and then eventually to 9i RAC.
After we move on to raw (without OPS), may be
Mark,
Thanks for the reply. We are on AIX 4.3.
We are not changing hardware when we move on to RAW devices. Our entire
hardware is going to remain same.
We feel dd is the fastest method of copying the files. But we need to figure
out how many blocks
we should skip in raw devices.(point 2 in
Joe,
We are planning to move to RAC. Per Oracle RAW devices is must for RAC.
As you said, Yes there is little performance gain just moving to RAC and
more work to DBA's/SA's.
But this seems to be the main requirement for RAC.
- Original Message -
To: Multiple recipients of list
Nat, totally understand.
joe
Nat wrote:
Joe,
We are planning to move to RAC. Per Oracle RAW devices is must for RAC.
As you said, Yes there is little performance gain just moving to RAC and
more work to DBA's/SA's.
But this seems to be the main requirement for RAC.
- Original Message
Nat-
You may want to check out a product from Veritas.. *Supposedly* their
clustered file system product is *approved* with 9i RAC on a SUN platform..
This is strictly from the rumor mill and I have no solid documentation to
confirm (CYA).
I am actually in the beginning phases of a project to
Nat - I haven't worked with raw for a few years, but from my dim
recollection, since you are managing what is on the device, first the system
administrator had to tell me how many blocks I could write to. I also dimly
recall the AIX issue, but certainly couldn't recall the answer. Anyway, this
Dennis,
We are thinking of doing following steps for our RAW conversions.
Let me know whether it makes sense,
1. Shutdown Database.
2. Take Full Backup
3. Setup all our raw devices ( properly corresponding to our original
filesystem datafiles.)
4. Bring up the database in restricted mode.
4.
I would change to the following:
[EMAIL PROTECTED] 09/20/02 03:09PM
Dennis,
We are thinking of doing following steps for our RAW conversions.
Let me know whether it makes sense,
1. Shutdown Database.
2. Take Full Backup
3. Setup all our raw devices ( properly corresponding to our original
Nat - I think your process looks fine, bearing in mind that I haven't used
raw devices in years. Others on the list use raw on a daily basis, so may
offer some suggestions.
My question was much simpler. Suppose I have a 80-gig. device, and a
20-gig. datafile. Okay, my recollection is that I
Just keep in mind that you can not offline system tablespace ;)
- Kirti
-Original Message-
Sent: Friday, September 20, 2002 2:44 PM
To: Multiple recipients of list ORACLE-L
Nat - I think your process looks fine, bearing in mind that I haven't used
raw devices in years. Others on the
Denis,
Sorry I missed your main question last time. Each datafile in our database
will represent a separate raw device. so question of overwriting files will
never come. If I have 30 datafiles in 5 files systems, I will be creating
30 raw devices with properly sized devices to match my
Another option is to shutdown db, backup the files to tape, remove filesystems, create
symbolic links named the same as your datafile names linked to the raw devices,
restore files to symbolic links (i.e. raw devices), startup db. Just a thought.
Gene
[EMAIL PROTECTED] 09/20/02 04:20PM
Nat - Thanks for taking the time to explain that. As I said, it has been
quite some time since I worked with raw, and at that time the system admin
just gave me a single mount point for the entire device. Best of luck with
your project, sounds like you've planned well, but don't skip that full
Nat,
SQL-generating-UNIX commands works well...
select 'dd bs=1024k if='||name||' of=/dev/rX' from v$datafile
union all
select 'dd bs=1024k if='||member||' of=/dev/rX' from v$logfile
union all
select 'dd bs=1024k if='||name||' of=/dev/rX' from v$controlfile;
Nat - I'm assuming you can connect raw devices to your existing system.
Myself, I would create new tablespaces and datafiles on the raw devices.
Preferably you will use LMT with uniform extents. Then I would use CREATE
TABLE AS SELECT NOLOGGING to move the data. Personally I prefer to first
Hi Nat,
As long as you are not changing hardware platforms, you can use dd. (Of
course, I assume you're on some flavor of unix, since you didn't mention
OS.)
You can just do 'dd if=/path/to/filsystem/datafile
of=/path/to/raw/volume'.
Of course, your database must be down.
-Mark
On Thu,
18 matches
Mail list logo
