RE: transportable tablespaces on a SAN

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@xxxxxxxxxxx
http://www.gridapp.com



-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx 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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] 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.

Other related posts: