RE: V$ access for production support

  • From: <Jay.Miller@xxxxxxxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 14 Sep 2006 17:13:52 -0400

Add me to the group that grants access to query the views but puts a
strict resource limit on through the profile. 

As others have said, the developers know the application best.  We went
through about a 6 month period where developers (per senior management
edict) were not allowed any access to the production servers.  So when a
batch job malfunctioned they'd come up to my desk and they'd tell me
what to type to check what data had been processed so far, etc.  I'm
very happy that this edict was eventually revoked.

On the other hand, many years ago I had a production database *crash*
because someone was running a huge query that was doing full table scans
and sort-merge joins on about 6 different 100 million row tables.  That
was when we instituted the resource limits...

Jay Miller
Sr. Oracle DBA
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Michael McMullen
Sent: Tuesday, September 05, 2006 10:31 AM
To: Dave.Herring@xxxxxxxxxx; oracle-l
Subject: Re: V$ access for production support

How about v$session_longops? It's not a restricted view and it's
supposed to 
be used to monitor progress of long running queries/transactions?




Other related posts: