Thank You Pete.
"Pete Finnigan" <pete_at_petefinnigan.com> wrote in message
news:AN7YgBBhGvE$EwVM_at_peterfinnigan.demon.co.uk...
> Hi Brian,
>
> <snip>
> I have table 'emp' and users select from this table some info.
> Now I want to now what is the user name who select and SQL statement
> contensts.
> </snip>
>
> I suggested FGA because the poster wants to trap "selects" and he wants
> to see the SQL statements that are generated. Regular audit does not
> record the SQL statement used hence will not work for his requirements.
>
> kind regards
>
> Pete
>
> In article <3F12DB4E.3DC7F21A_at_remove_spam.peasland.com>, Brian Peasland
> <dba_at_remove_spam.peasland.com> writes
> >Why FGA when simple auditing will do the trick??? Isn't this making it
> >harder than it has to be? Or using a new feature when an old feature
> >will do?
> >
> >FGA will tell you when someone has accessed specific rows of data from a
> >table. Regular auditing will let you know when someone has accessed a
> >table for any row.
> >
> >Cheers,
> >Brian
> >
> --
> Pete Finnigan
> email:pete_at_petefinnigan.com
> Web site: http://www.petefinnigan.com - Oracle security audit specialists
> Book:Oracle security step-by-step Guide - see http://store.sans.org for
details.
Received on Tue Jul 15 2003 - 01:05:07 CDT
