Re: Testing Refresh Procedure

From: Dennis Williams <oracledba.williams_at_gmail.com>
Date: Wed, 22 Mar 2006 16:06:27 -0600
Message-ID: <de807caa0603221406i7a23bd0bt36d8db0693ea3949@mail.gmail.com>

Chugh,

My requirements is also similar where I have to refresh the lower regions
> (databases - development,system,acceptance etc.) from production data but
> not the functions,procedures,packages etc. very frequently. I use exp, and
> imp data after disabling triggers,fk constraints and truncating tables.
>

The advantage of cloning techniques compared to export/import is that you receive an exact replica of the production system. Why would you want to exclude functions, procedures, packages, etc.? The idea is that before a change is promoted to production it is tested against a current copy of production. The worst circumstance is that you promote something to production only to discover after much anguish that production has a different version of a function, procedure, package, or etc. than the test database.

Dennis Williams

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Mar 22 2006 - 16:06:27 CST