Re: Q: letting users see v$process table
Date: 1997/11/23
Message-ID: <658n00$96e_at_mtinsc03.worldnet.att.net>#1/1
I would say that you have three options. I list them in order from "worst" to "best". Note that they are EITHER/OR, i.e. use 1 OR 2 OR 3, but not any combination.
- Grant the admin user the SELECT ANY TABLE system privilege (Ouch !)
- Have the admin user run the $ORACLE_HOME/rdbms/admin/catdbsyn.sql script (creates private synonyms for the V_$ tables).
- As user SYS, run the script $ORACLE_HOME/rdbms/admin/utlmontr.sql. This script creates the MONITORER role. The role is granted SELECT privilege on all the V_$ tables accessed by the character-mode SQLDBA (remember it ?), including V_$PROCESS. Note that the script grants the MONITORER role to PUBLIC, so you may want to remove/comment out that line from the script before running it (or revoke MONITORER from PUBLIC afterwards). Then grant the MONITORER role to that admin user.
Hope this helps.
Michael Serbanescu
On 21 Nov 1997 09:26:30 -0500, gsa_at_panix.com (Gary Assa) wrote:
>I have a script that list some information on processes that I want an admin
>user who is collecting data to find out what processes are dead, inactive,
>etc.
>
>The only way to access v$process, as far as I can see is from the system
>account, and by DBA rule #2, I will not give out the password for that acocunt.
>I canot seem to create a view, and a public synonym does nothing. What is a
>solution?
>--
> ------------------------------------
>If you have a condom and sunscreen SPF 15 or greater, than it's safe to look at
> http://www.panix.com/~gsa/index.html
Received on Sun Nov 23 1997 - 00:00:00 CET