How to handle refreshing TEST schema with PRODUCTION schema ?

Question

- we have database 10g ( standard edition), database name : ABC
- Schema name: ABC.PRODUCTION (which is our production schema)
- Schema name: ABC.TEST (which is our testing schema, where developers work)
Both the production & Test schemas exist in the same database.
Now once a week I wanted to refresh TEST schema with PRODUCTION data
Here is what I have been doing all these years:
=> Take a logical backup (EXPDP) of PRODUCTION schema (prod.dmp)
=> Drop user TEST cascade ( i don't need a backup of this TEST schema)
=> Create user TEST
=> Import PROD.DMP data into TEST schema
All the above 4 steps are being done manually.
Questions:
======
1. Is there any easier way of doing the above steps using some tool ?
2. Does Oracle enterprise manager which comes free with database installation (http://localhost:118/em)
has any utility or tool to do this job ?
3. I want everything to be refreshed (all database objects including data) ?
Thanks
John P
Edited by: johnpau2013 on Feb 23, 2011 4:32 AM

Answer 1

This is crazy. One inadvertent typo and you'll overwrite your Production schema. Plus, what happens if a developer 'tests' against the test schema and slows the Production database to a crawl.
I presume you know all about this, though and can't make the case to management. I hope it's not a business-critical Production database!
Anyway, your method is decent. I would advise against doing it automatically, to be honest, especially when your system is so precariously set up. But if you exist, you could use encapsulate all the steps into a script and use crontab to automate the process. I, personally, wouldn't use DBMS_SCHEDULER as you have to be careful with priorities and workload sometimes (at least in my experience) and you might end up having your export/import clash with other jobs in the system if you don't pay attention.
Here are the steps I would use:
Create a 'create user' script for the test schema based on dynamic SQL. That way you can be sure you have all the grants necessary for the user, in case things change.
Drop the test user (use EXTRA caution and be defensive when coding this part!)
Export the schema using FLASHBACK_SCN to ensure you have a consistent export
Run your 'create user' script to create the test user
Import the schema with a REMAP_SCHEMA option (use EXTREME caution with this!!!!)
Compile invalid objects
Compare objects and exclude any recycle_bin objects. Send an email alert if the object counts are different.
Compare invalid objects. Any objects which aren't invalid in Production should be flagged up if they're invalid in test.
Again, it's absolute insanity to have a test schema in a Production database. You absolutely must insist on addressing that with management.
Mark