On May 5, 11:00=A0pm, "Ana C. Dent" <anaced...@[EMAIL PROTECTED]
> wrote:
> m...@[EMAIL PROTECTED]
wrote innews:NsKTj.1754$ah4.1745@[EMAIL PROTECTED]
>
> > I would like to allow developers to kill their own sessions, e.g.
>
> > =A0 =A0 alter system kill session '$sid,$serial#'
>
> > but only for sessions which are theirs.
>
> > Is there a grant which can handle this? =A0If not, what's the
> > best way to handle this?
>
> You can write a procedure owned by SYS which can issue the ALTER SYSTEM;
> using owner's rights not invoker's rights.
I also agree with the stored procedure route; however, the owner does
not need to be SYS and probably should not be SYS. I created a DBA
privileged account to own special purpose routines like this. Using a
non-SYS owner makes keeping track of the special purpose routines,
database event triggers, and like easier.
IMHO -- Mark D Powell --
|
