Re: quick qestion about logon/logoff triggers - does system have to own them?

On Sep 26, 9:59 am, GS <G..._at_GS.com> wrote:
> In order to keep the SOX beancounters-from-hell(Auditors) at bay I have
> to provide a report for my boss that shows who logged on to which
> database, from which machine, to which database, with which app, etc.
>
> I plan on putting in a simple table that will get populated by two
> triggers, one after login and one before logoff.
>
> Do the logon/logoff triggers have to be owned by system or sys? I was
> thinking I'd create an "audit" user with its own tablespace (or use the
> tools tablspace) and keep the table out of the system/sys schemas.
>
> Out of curiousity, how much of a PITA has it been for anyone else out
> there implementing SOX, and to what lengths did you go to become compliant?
>
> thanks

Which release of Oracle are you using? If it's 9.0.1.x or later you can implement such tracking using 'AUDIT SESSION;'. Records are written to DBA_AUDIT_SESSION and are easily queried; logon, logoff and some selected statistics are captured for each session.

If you're using 8.1.7.4 or earlier then you'll need the table/triggers combination you're considering, and, yes, these need to be owned by SYS. David Fitzjarrell Received on Wed Sep 26 2007 - 10:44:16 CDT