Re: Stale procedures?

No.

UserB should be kicked off the system during the upgrade ... which should be done in a responsible manner after hours or on a weekend by UserA.

That anyone is mucking around with production code during the workday is absolutely inexcusable short of a total system failure. I would show UserA to the door if they were in my department and did even once.

Daniel A. Morgan

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 Thu Apr 12 2001 - 22:46:24 CDT