RE: V$ access for production support

  • From: "Herring Dave - dherri" <Dave.Herring@xxxxxxxxxx>
  • To: "Tanel Poder" <tanel.poder.003@xxxxxxx>, "Christian Antognini" <Christian.Antognini@xxxxxxxxxxxx>
  • Date: Sun, 3 Sep 2006 10:04:46 -0500

HAH!  I knew I was paranoid for a reason (just didn't know the reason!).
In the past I've had problems where I gave developers monitoring tools,
to help them see what are the biggest resource hogs.  Eventually they
all ran the tools continuously, making the resource hogs their processes
monitoring resource hogs.

Dave Herring, DBA
Acxiom Corporation
3333 Finley
Downers Grove, IL 60515
wk: 630.944.4762
"When I come home from work and see those little noses pressed against
the windowpane, then I know I am a success" - Paul Faulkner

> -----Original Message-----
> From: Tanel Poder [mailto:tanel.poder.003@xxxxxxx]
> Sent: Sunday, September 03, 2006 9:33 AM
> To: Herring Dave - dherri; 'Christian Antognini'
> Cc: 'oracle-l'
> Subject: RE: V$ access for production support
> Well someone malicious could cause some library cache latch contention
> running PL/SQL or nested loop joins against unindexed columns of V$SQL
> So you'd need to:
> 1) work out which views would actually be needed for production
> 2) distinguish which views are dangerous and which are not and create
> roles based on that
> 3) give respective roles to the users based on how much you trust them
> Tanel.
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be
legally privileged.

If the reader of this message is not the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank you.

Other related posts: