Using the user audit table to generate reports can provide a wealth of information that may prove to be critical to you as an Oracle administrator.Our first report is a summary of total session time, shown in Listing D.In order to properly design these triggers, let's begin by looking at the information that's available inside the system-level triggers.First, we'll gather the information provided at login: Since the user logon/logoff triggers are separate entities, we have several choices in the design of a table to support this information.
As you might imagine, this is tricky because you may have many users who are signed on with identical user names.
HIPAA, the Sarbanes-Oxley Act, and the Gramm-Leach-Bliley Act have all produced serious constraints on Oracle professionals who are now required to produce detailed audit information for Oracle system users.
federal laws have mandated increased security for auditing Oracle user activity.
We can use this session ID as a primary key to update our user audit table with logoff information.
Now let's look at the information that becomes available as a result of using our logoff trigger.