Re: Cloning an Oracle instance

In article <37d6adc6.11640759_at_news.columbia.edu>, k_a_h_l_i_l_at_yahoo.com wrote:
>You'll have to export/import, and THEN manually change the tablespaces
>that contain your object-- ie. you can't import into a different
>tablespace, if I remember correctly. That means that you might as well
>export the whole thing, then import the whole thing, and then do your
>tablespace re-arrangement.
>
>On 9 Sep 1999 00:02:54 GMT, "Lizzie"
><GreenRaven_at_worldnet.spamless.att.net> wrote:
>
>>Hi - I need to clone an Oracle instance to another... different directories. ...

We do this by means of a restore followed by rebuilding the control file with an edited script generated by backing up the original database's control file with the ALTER DATABASE command. A bit tricky but not hard when you get used to it, and it's good practice. Also faster than exporting and importing a big database.

However, if you still want to use exp and import, here's what I suggest. First, create your target database and create the tablespaces in the directories you want (it helps to have a tool that will generate the DDL you need from your source database, then edit the filenames to change their directories). Then import the .dmp file with IGNORE=Y and DESTROY=N to put all the tables, indexes, etc. into the tablespaces you built. Provided the tablespaces can have the same names in the target as they did in the source, their directories don't matter since you've taken care of that manually already.

Paul de Anguera | "You can't write a chord ugly enough to say
Reply to:       | what you want to say sometimes, so you have to
deanguer@       | rely on a giraffe filled with whipped cream."
quidnunc.net    | - Frank Zappa