| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: V$ access for production support
Welllll, I'd like to say I had a great reason, but so far I've only come
up with being paranoid. I guess I could create a role and grant privs
on those V_$ views I need to, then grant the role to those needing
access for production support. Sure a lot easier than creating wrapper
procedures per SQL statement!
Glad I asked.
Dave
"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: Christian Antognini [mailto:Christian.Antognini_at_trivadis.com]
> Sent: Sunday, September 03, 2006 2:49 AM
> To: Herring Dave - dherri
> Cc: oracle-l
> Subject: RE: V$ access for production support
>
> Dave
>
> > Ideally
> > they'd have access to V$TRANSACTION and V$SESSION to get basic
> > transaction information to track progress when it seems to be
> > running long, but I'm reluctant to start granting access to V$ views
> > on a production database.
>
> Which is the reason? The only security issue I see is that the support
> guys are able to see literals and, to some extents, bind variables
that
> are in the SGA. But if they have access to the data as well, this
> doesn't increase, usually, the amount of information they can
access...
> So, it would be interesting to know why you don't want to give access
to
> those views.
>
>
> HTH
> Chris
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.
-- http://www.freelists.org/webpage/oracle-lReceived on Sun Sep 03 2006 - 09:13:16 CDT
 |
 |