Re: Who to copy complete database

Ulrich:

As I see it, you have 2 choices. You can "clone" the database or you ca= n
rebuild it from scratch, in the new environment and import the data from = the
production environment into the new database (as you alluded-to).

Which choice you make depends on what sounds good to you.

Cloning Advantages:
  Fast

Import Advantages
  Allows compression of extents and miscellaneous cleanup.   Allows you to make your datafiles SMALLER than those in the production environment.

At our site we rebuild our TEST database(s) about every 60 days. I ALWAY= S use
the Import method for the advantage I described. You didn't say how big = your
database is. Our production is about 20GB and I can rebuild it with an i= mport
in < 24 hours.

I wrote an article that appeared in the OAUG Insight Magazine this quarte= r on
Successful Migration of Oracle Applications Database.

"Choose your poison" and let us know.

-Jim Basler
Oracle Database Administrator,
Intervoice, Inc.

Ullrich wrote:

> Dipl. Biochem. Jonas Ullrich
> Eberhardstr. 11, D-72072 Tübingen
> T: +49 70 71 35 74 6, F: +49 70 71 35 71 8
> E-mail: Jonas.Ullrich_at_tuebingen.netsurf.de
>
> Please help me.
>
> We use a Oracle 7.0 database on a "production" server. We connect norma=
lly
> to another "development" server, to test our applications. In the meant=
ime
> the data in this database are not compatible to our "production" databa=
se.
> I have no administration experience. What to do, to copy the complete
> "production" database to the "development" server. Is it necessary to c=
reate
> a new database and import the *.dmp-Files or is there any easier way, f=
or
> example copy complete directories via network?
Received on Fri Nov 13 1998 - 13:25:33 CST