From: Doug Coan <dcoan@aegonusa.com>
Subject: Re: Export and Import and Referential Integrity Constraints
Date: 2000/08/08
Message-ID: <8mpjpf$ann$1@nnrp1.deja.com>#1/1
References: <3974CC75.D9C80394@yahoo.com>
X-Http-Proxy: 1.0 x73.deja.com:80 (Squid/1.1.22) for client 206.150.248.11
Organization: Deja.com - Before you buy.
X-Article-Creation-Date: Tue Aug 08 18:33:18 2000 GMT
X-MyDeja-Info: XMYDJUIDdougcoan
Newsgroups: comp.databases.oracle.server
X-Http-User-Agent: Mozilla/4.72 [en] (WinNT; U)


In article <3974CC75.D9C80394@yahoo.com>,
  Boo <Boo@yahoo.com> wrote:
> Running Oracle 8.0.5 on Solaris 2.7.
> Is there any reasons why, when moving a database with quite a few
> referential integrity constraints to a new server, that the
> export/import option
> can't be used?
> My understanding is, if it's a fresh database built on the new server,
> and doesn't have existing data, than an export/import should not pose
> any problems.
>
> TIA
>
>


Using import/export is, in my opinion, the preferred method for moving a
database to a new server especially if you are moving to a new version
or patch level.  I use this regularlly not only for the initial load,
but if you are in a parallel environment, to do periodic shcema level
updates to keep the dbs in sync until cutover.


--
Doug Coan
Oracle Certified Professional DBA


Sent via Deja.com http://www.deja.com/
Before you buy.