RE: How to move 200 GB db from prod to dev?

[Magaliff, Bill]

Title: How to move 200 GB db from prod to dev?

1) use RMAN to clone the db; or

2) create the new dev db with the required users but without all the data/index tablespaces, and use transportable tablepsace feature to move tablespaces/data files . . . export/import of meta-data is quick - only real time factor is copying the data files - this assumes, of course, that you can make your production tablespaces read-only for the time it takes to copy (or tar) the data files

 

-bill

-----Original Message-----
From: Daiminger, Helmut [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 06, 2002 10:28 AM
To: Multiple recipients of list ORACLE-L
Subject: How to move 200 GB db from prod to dev?

Hi!

We are supposed to clone our production database onto a new development box (both boxes are Sun Solaris). The db is about 200 GB in size.

What would be the best way to achieve this? Simply copying over the files won't work, since the instance names are different:

Production:  SID=PCLDB1 => e.g. /u02/oradata/PCLDB1/system01.dbf
Development: SID=ROLAND => e.g. /u02/oradata/ROLAND/system01.dbf

So would export/import the entire db be the only way? (But writing out dump file that big should be a little disk space problem...)

Renaming all the datafiles (approx. 100) would be kind of annoying...

Any ideas?

This is 8.1.7 on Sun Solaris.

Thanks,
Helmut