RE: transportable tablespaces on a SAN
Date: Sat, 6 Jun 2009 10:07:08 -0400
Message-ID: <C0A5E31718FC064A91E9FD7BE2F081B101D4B96D_at_exchange.gridapp.com>
Plus you'll need a CFS or use raw devices if you want to have multiple hosts accessing the same physical filesystem/disk devices.
Matt
--
Matthew Zito
Chief Scientist
GridApp Systems
P: 646-452-4090
mzito_at_gridapp.com
http://www.gridapp.com
-----Original Message-----
From: oracle-l-bounce_at_freelists.org on behalf of Michael McMullen
Sent: Fri 6/5/2009 2:41 PM
To: 'ORACLE-L'
Subject: RE: transportable tablespaces on a SAN
I guess you mean you have two separate servers, and you want to do something like export the metadata, drop the tablespace from db 1 (but not the datafiles) and then transport db 1 tablespace into db 2? You don't mean keep both tablespaces in both databases using the same datafiles, right?
A lot of details missing here but doesn't this sound like nothing but trouble? How slow can a copy from the same SAN be?
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Thomas Day
Sent: Friday, June 05, 2009 1:37 PM
To: ORACLE-L
Subject: transportable tablespaces on a SAN
I have two databases, both using the same SAN for their datafiles. Assuming that they can both see the same logical drives, can I transport a tablespace back and forth by just do the metadata exp/imp?
What I'm hoping is that I don't have to copy the datafiles.
--
http://www.freelists.org/webpage/oracle-l
Received on Sat Jun 06 2009 - 09:07:08 CDT