RE: REPLICATION (816) of functions/procedure

  • From: "Mark W. Farnham" <mwf@xxxxxxxx>
  • To: <wisernet100@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 3 Sep 2004 13:19:39 -0400


You make an excellent point. In fact periodic source code extraction for
differencing against the checked in, approved production release or some
variant on that theme should be part of the audit policy. When you find a
difference that was not processed through change management (at least as an
emergency, meaning logged but no review until later), then you start looking
for an explanation. Most folks I work with have change management policies,
and nearly all of them do after I work with them. Definitely, what is in use
is in dba_source, and managing that it matches what is checked in in the
change management system is only as good as adherence to and correctness of
the change management system.

Also, in case the OP was thinking there might be some automated replication
of stored functions and procedures, I'm not aware of any built in way to do
that in Oracle. Many consulting firms and individual companies construct
various "move-ups" systems that propagate code to the desired
destination(s). Usually these get tailored to individual installations.


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Rachel Carmichael
Sent: Friday, September 03, 2004 8:34 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: REPLICATION (816) of functions/procedure

May I make the point that having the script source in no way ensures
that you have the code as it is in the database you are copying from?

There are way too many people who make "quick fixes" without updating
source repositories. I've been known to do that myself, I freely admit.

I *always* take the source code from dba_source when I am replicating
packages/procedures/functions. This may be a case of DBA paranoia but
it takes no more time than pulling code from a source code repository
and allows me to sleep through the night after a change. There are
several good programs available (some free, some cost) that do that
easily and quickly.


--- "Mark W. Farnham" <mwf@xxxxxxxx> wrote:

> Well, first I hope you actually have the script source used to create
> them
> originally.
> If not, you should be able to get the code out of dba_source.

To unsubscribe - mailto:oracle-l-request@xxxxxxxxxxxxx&subject=unsubscribe 
To search the archives -

Other related posts: