RE: Method for migrating schema from PROD to DEV
- From: "Michael McMullen" <ganstadba@xxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 5 Feb 2009 11:42:08 -0500
Your method is fine, you can also use impdp over a db link which avoids a
dmp file. Also watch for user created jobs if you are doing the migration
via a different user as impdp will create the jobs under the user doing the
import which I think should have been fixed in 10.2.0.4 impdp
_____
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of SHEEHAN, JEREMY
Sent: 24 November 2008 21:12
To: oracle-l@xxxxxxxxxxxxx
Subject: Method for migrating schema from PROD to DEV
Does anyone have a proven method for migrating a schema from PROD to DEV? I
plan on using export/import, but I've got a few reservations about the
migration steps.
I think the best method would be to do the following
1. Export Schema in PROD
2. Export Schema in DEV (for backup)
3. Drop user in DEV
4. Create basic user in DEV
5. Import user in DEV
6. Verify object count - PROD vs DEV
7. Compile schema
Does this sound right?
Jeremy
P Consider the environment. Please don't print this e-mail unless you really
need to.
______________________________________________________________________
Wm Morrison Supermarkets Plc is registered in England with number 358949.
The registered office of the company is situated at Gain Lane, Bradford,
West Yorkshire BD3 7DL. This email and any attachments are intended for the
addressee(s) only and may be confidential.
If you are not the intended recipient, please inform the sender by replying
to the email that you have received in error and then destroy the email.
If you are not the intended recipient, you must not use, disclose, copy or
rely on the email or its attachments in any way.
Wm Morrison Supermarkets PLC accepts no liability or responsibility for
anything said in the email or its attachments and gives no warranty as to
accuracy. It is the policy of Wm Morrison Supermarkets PLC not to enter into
any contractual or other obligations by email.
Although we have taken steps to ensure the email and its attachments are
virus-free, we cannot guarantee this or accept any responsibility,
and it is the responsibility of recipients to carry out their own virus
checks.
______________________________________________________________________
Other related posts:
