Migrate everything from test database to production in 11.2.0.2

Please advice and provide for the best method and steps in details for migration from test database to production.
lium1Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
slightwv (䄆 Netminder)Connect With a Mentor Commented:
I'm afraid we need more information.

Things like Size of database, what objects you are migrating, etc...

Off the top of my head, I would look at export/import.  Just export the schemas you want moved over and import them into the production database.
0
 
MikeOM_DBAConnect With a Mentor Commented:
Adding to the above:

* clone db using Rman
* clone db using data file copy
* create new prod db and use transportable tablespaces
* use datapump like slightwv's suggestion
:p
0
 
lium1Author Commented:
SlightWV,

Basically, moving everything from test to production.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
PaulConnect With a Mentor Commented:
'moving everything'

Double-check table contents:

Some tables may contain test data that should not be migrated. e.g. in testing there may be 'customers', 'orders', 'invoices' etc that are all bogus - and should never be in production.

On the other hand other tables may require the data (e.g. for lookup values).
0
 
slightwv (䄆 Netminder) Commented:
>>Basically, moving everything from test to production.

This doesn't answer the questions I posed.  

"Everything" could be 3 tables or 3000 tables.
It could be 100 Meg of data or 300 Terabytes of data.
It could be one schema or 100 schemas.
0
 
lium1Author Commented:
I meant all data plus schemas, tables (data files), etc ., and it is 500 gig of data.
0
 
slightwv (䄆 Netminder)Connect With a Mentor Commented:
For 500 Gig I would look at cloning as suggest by MikeOM_DBA.

I would probably go with RMAN duplication:
http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#RCMRF126

Then change the name of the database when you restore in production.

If you are comfortable with Oracle, you can manually clone the database.

There are many blogs/links out there on how to clone an Oracle database and restore to a different server as well as changing the name once you've restored.
0
 
MikeOM_DBACommented:
And...
Consider PortletPaul's suggestion to clean-up test data.
0
 
lium1Author Commented:
Thanks guys!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.