Xref: alice comp.databases.oracle.misc:40645 comp.databases.oracle.server:65131
Newsgroups: comp.databases.oracle.server,comp.databases.oracle.misc
Path: alice!news-feed.fnsi.net!newsfeed.eurocyber.net!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!dca1-hub1.news.digex.net!intermedia!lynx.unm.edu!jobone!news.er.usgs.gov!news
From: Brian Peasland <peasland@edcmail.cr.usgs.gov>
Subject: Re: Cloning an Oracle instance
Content-Type: text/plain; charset=us-ascii
Message-ID: <37D7C41B.C74C2A11@edcmail.cr.usgs.gov>
Sender: news@igsrsparc2.er.usgs.gov (Janet Walz (GD) x6739)
Content-Transfer-Encoding: 7bit
Organization: Raytheon Systems
X-Accept-Language: en
References: <01befa56$c5b8b2e0$d8b44f0c@liznet.bcgroup.com>
Mime-Version: 1.0
Date: Thu, 9 Sep 1999 14:28:43 GMT
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
Lines: 20

Lizzie,

> I need to migrate all the objects from this instance, including packages,
> package bodies, views, etc.
> I'm planning on using Export (does Export do packages?) , but not with a
> "full" option because I want to put the objects in the tablespaces
> belonging to the new instance, which will be in different directories.

I would do a full export. That way, everything in the database is in
your export file. Just because you do a full export doesn't mean that
you have to import everything. You can pick and choose which objects to
import from the file. 

If the tablespaces on the new instance are named the same as the old
instance, you will not have any problems. Importing an object should
place it in the same tablespace name. Placing the object in a different
tablespace is slightly more complicated. 

HTH,
Brian