AAAHHH. Fire them. Except of course you probably can't do that.
How about this:
1. Write a trigger to capture who did it and log that to a table. So you
can later send an email to them and their manager stating why they are
putting the system in jeopardy. (use autonomous transaction and user is the
variable that will tell you who)
2. Put a constraint on the row to only allow the current password. So an
error will get raised if anyone tries to change it.
3. Could put a trigger that calls a wrapped pl/sql routine to confirm that
the value is good and if it isn't then log it and raise an error which would
rollback the transaction.
Jim
"George Mansoor" <ghm_at_4link.net> wrote in message
news:10ae5iqko0j0209_at_corp.supernews.com...
> It's a security table in PeopleSoft. Trying to prevent security admins
from
> changing the password for the application server account. Policy and
other
> mechanisms haven't proven to be successful in getting folks to leave this
> account alone. If the account is changed, then the application servers can
> shutdown or not restart if booted.
>
> Thanks
>
> George
>
> "Jim Kennedy" <kennedy-downwithspammersfamily_at_attbi.net> wrote in message
> news:0Supc.98650$Ik.7706154_at_attbi_s53...
> >
> > "George Mansoor" <ghm_at_4link.net> wrote in message
> > news:10ack1ntmj9vl03_at_corp.supernews.com...
> > > Is there a way to lock one row of data from all users, permanently?
> > >
> > > Thanks
> > >
> > > George
> > >
> > >
> > For what purpose? What are you trying to achieve? What is the business
> > need? Maybe there is a better way.
> > Jim
> >
> >
>
>
Received on Sun May 16 2004 - 02:53:22 CDT
