RE: Permission to see the procedures
- From: "Post, Ethan" <Ethan.Post@xxxxxx>
- To: <Michael.Kline@xxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 10 Feb 2005 14:32:10 -0600
Why wouldn't you just throw up a copy of the database (perhaps no rows)
someplace else for them? Or extract the code someplace in the event
they want to view it (to text files).
Why would they need direct access to the code in the production
environment?=20
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kline.Michael
Sent: Thursday, February 10, 2005 2:21 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Permission to see the procedures
The development folks would like to be able to view the procedures,
packages, etc., on a production reporting database, but we do *NOT* want
them to be able change anything.=20
=20
This is sort of like a "read only" access to packages, procedures,
triggers, etc.
=20
=20
I would think this would be like a "select any view" but I don't see any
thing there.
=20
Can this be done by granting some sort of privs to a role and then
giving them the role?
=20
Michael Kline
Database Administration
SunTrust Technology Center
1030 Wilmer Avenue
Richmond, Virginia 23227
Outside 804.261.9446
STNet 643.9446
Cell 804.744.1545
<mailto:michael.kline@xxxxxxxxxxxx> michael.kline@xxxxxxxxxxxx=20
************************************************=20
The information transmitted is intended solely=20
for the individual or entity to which it is =20
addressed and may contain confidential and/or=20
privileged material. Any review, retransmission,=20
dissemination or other use of or taking action=20
in reliance upon this information by persons or=20
entities other than the intended recipient is=20
prohibited. If you have received this email in=20
error please contact the sender and delete the=20
material from any computer. [ST:A234]=20
************************************************=20
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
