| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: How to refresh
The methodology we developed for one client goes like this:
There are three databases - dev, test, and prod.
dev starts as a clone of prod, and fixes, changes and enhancements are developed and unit tested there. One of the REQUIRED products of development is a script that will upgrade prod to the new version.
When we are ready for complete testing of a new version of the entire application, test is recreated as a clone of prod.
We run the upgrade script against test. If there are any problems, errors, missing stored procedures, or other missing or incorrect versions of database objects after running this script, the script must be corrected, and we start over with a fresh clone of prod. By the way, VERY IMPORTANT: Data changes, such as new, updated or deleted rows in code or control tables are part of the upgrade, not just DDL changes.
Once the upgrade script has been run, test is a version beyond prod, and can be tested thoroughly. If errors are found they are corrected and unit tested in DEV, not test, and then put into a corrected upgrade script, we may then correct test from the script, but testing is NOT complete until test is recreated as a clone of prod yet one more time, and upgraded with the script, and run through a battery of tests again.
By the time we finish testing, all we should have to do is run the upgrade script against prod and bring prod live in the new version. Then we'll often recreate dev as a clone of prod.
-----Original Message-----
Sent: Tuesday, December 16, 2003 9:55 AM
To: Multiple recipients of list ORACLE-L
I need to do a refresh of a test database using production data. We use import for this. In the past we have always dropped the schemas (4 or 5), recreated the schemas, and then did a full import with ignore=n. This time the user does not want to lose any of the new functions and procedures that are in test, but not in prod. Instead, they would like to just refresh the table data. Last time we tried this we had all kinds of trouble with functions, triggers, constraints, etc... and ended up doing a full import.
Is there a tried and true way to just refresh the table data without losing anything else and without having all the problems with triggers and constraints?
Thanks!
Ron
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: John Flack
INET: JohnF_at_smdi.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services ---------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Tue Dec 16 2003 - 11:34:25 CST
 |
 |