Re: full database import

Mark,

Thank you very much for answering my question. I have a much better understanding
of full database cloning after having reading a number of technical articles.

The copy database is on the same machine as the orginal but with a different name and is running 8.1.6.
However, one question remains after I did one experiment and read the oracle documentation.
The following is what I did:

1. I have a database called FIRST with its datafiles stored in a directory called d:\oradata\first\.
2. I then created a second database called SECOND with all the datafiles in d:\oradata\second\
3. I exported database FIRST to a dump file (using exp system/manager full=y file=clone.dmp...)
4. I then imported the dump file to database SECOND (using imp full=y destroy=y ignor=y file=clone.dmp...)
5. I checked database FIRST and it is ok. ( all its files still in d:\oradata\first\ directory)
6. I checked database SECOND and it is ok and is exactly same as FIRST (all its files are in d:\oradata\SECOND\ directory. conclusion is cloning a database using import doesn't destroy the original database.

The conclusion is in contrast with what Oracle documentation indicated. Import utility guide mentioned that what I did would overwrite the orginal database;
I also opened the dump file and reviewed all the codes inside that file. it seems that oracle documentation is right.

Can you shed some light on this?

Thanks

"Mark D Powell" <markp7832_at_my-deja.com> wrote in message news:9034kh$u4u$1_at_nnrp1.deja.com...
> In article <vg%U5.353840$4d.43902328_at_news02.optonline.net>,
> "W. Cao" <pdxbq_at_yahoo.com> wrote:
> > Could someone tell me how to use export/import to clone a database? I
 know
> > how to export a full datbase but don't know how to do a full database
> > import. Do I need to create a new database first? What is the general
 steps?
> >
> > Thanks.
> >
> > Wayne
> >
> Is the copy database on the same machine as the original? If not and
> the file systems look the same on the machine you can create the new
> instance with only a system tablespace and allow the full import to
> allocate all the tablespaces.
>
> However, it is generally better to create all the tablespaces manually
> and to place the datafiles where they best belong. If the old instance
> and new instance are on the same machine you should consider this is a
> requirement as you do not want the import to attempt to reuse existing
> datasets that belong to another instance. In the version 6 days
> failure to create all the tablespace in advance or to provide the
> destroy=n parameter to the imp utility would destroy the original
> database. Somewhere in version 7 Oracle changed the default setting of
> destroy to N from Y so you no longer have to worry about this. But I
> would always play it safe because defaults are subject to change with
> each release.
>
> --
> Mark D. Powell -- The only advice that counts is the advice that
> you follow so follow your own advice --
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Thu Nov 30 2000 - 21:00:05 CST