Re: Stale procedures?

Try using Packages. Packages rely on other Package Specifications not the bodies for compilation. Another package won't become invalid unless Package Spec changes therefore making changes to a Package Body and compiling won't invalidate other Packages.

This is a better implementation than the one you're using but I doubt it will solve all of your problems.

hth
Steve J.

Greg Weston wrote:

> I'll start off by saying I'm primarily an application developer and
> only a duffer as a DBA, so I hope this isn't too stupid a question.
>
> Consider the following situation:
>
> UserA has a bunch of tables and several stored procedures that add data
> to those tables. There are public synonyms to every object owned by
> UserA.
>
> UserB connects to Oracle and starts repeatedly calling one of UserA's
> procs. What this proc does is shove a bunch of raw data into one of the
> UserA tables and then call several utility functions to massage it and
> put it into other places. We'll call it InsertionBottleneck.
>
> UserA replaces one of the utility procs used by InsertionBottleneck and
> recompiles everything that's gone invalid.
>
> What we see now is that while the InsertionBottleneck function
> continues to populate the raw data table, the utility function no
> longer seems to be working. This will continue to be the case until and
> unless UserB breaks and reestablishes their connection.
>
> What I'm asking is: Is there a way to get things working again that's
> less drastic than breaking UserB's connection?
>
> Thanks in advance for any help.
>
> Greg
  Received on Mon Apr 16 2001 - 11:32:49 CDT