Re: Data transfer between two 8.1.6 databases, forgot to mention ...

If the requirement that the source tablespaces be in read only mode during the export does not make transportable tablespaces practical, l'd recommend the dblink and create table as select (CTAS) method, with an export (rows=n) from the source db and import to destination db to pick up any constraints/indexes/triggers,etc.

On Fri, 10 Nov 2000 05:26:44 GMT, Yurasis Dragon <yurasis_spam_at_yahoo.com> wrote:

>I have experimented with transportable tablespaces and
>can confirm that it's a good method of copying data from
>one database to another.
>
>One issue that is important and that may make this option impractical
>is that from the source databases, the tablespaces in question must be
>put in read only mode (alter tablespace <xxx> read;).
>
>
>On Thu, 9 Nov 2000 16:05:45 +1100, "Howard J. Rogers"
><howardjr_at_www.com> wrote:
>
>>Well, the documentation for 8.1.6 discusses it at the level of philosophical
>>principle in the Oracle concepts manual (technet.oracle.com has it if you do
>>a search for "TransportableTablespace" -find the section headed "Moving or
>>Copying a Tablespace to Another Database), and the Administrator's Guide has
>>all the specifics on how to do it (under the heading "Transporting
>>Tablespaces Between Databases").
>>
>>On my own website, the DBA Course slides has a chapter on Export and Import
>>(Chapter 15 from memory) which touches on the Transportable Tablespace
>>option, and there's equally a slide or two in the Backup and Recovery course
>>slides.
>>
>>Regards
>>HJR
  Received on Thu Nov 09 2000 - 23:32:25 CST