There are a couple ways of tracking logon and logoff information within an Oracle database, however few offer the simplicity and flexibility of the use of an logon and logoff trigger. Here is how I built a simple set of triggers and accompanying table to track usernames, logon time, logoff time, machine connected from and program used.
I performed these steps as system. If you want to install these as another user you will need to assign the appropriate permissions first.
The first step is to create a table to store the information. This table may grow quickly if this is a very active system so we want to put it somewhere other than the system tablespace. For reference, mine currently has around 3000 records in it and is around 200k in size. Of course mileage may vary.
CREATE TABLE session_audit
This will be the table you query to determine login information. Of course you will probably want to purge data from here occasionally to keep it from getting too big.
Next we create the logon trigger which will populate all but the logoff_time of the session_audit table. This uses the sys_context function to lookup the host and session id (different from the SID) of the session. The program is retrieved by a subquery on the V$SESSION table.
CREATE OR REPLACE TRIGGER tr_session_audit_logon
AFTER LOGON ON DATABASE
select sys_context('USERENV','SESSIONID') into session_id from dual;
IF session_id != 0 --ignore internal connections
INSERT INTO session_audit (
(SELECT program FROM v$session
WHERE sys_context('USERENV','SESSIONID') = AUDSID),
UPDATE: I have found that the old version of this resulted in an ORA-1427 error when someone made an internal connection. The problem also came up when dbms_jobs were run. The code now ignores internal connections (where the session id is 0).
Finally we create the logoff trigger to fill in the logoff_time.
CREATE OR REPLACE TRIGGER tr_session_audit_logoff
BEFORE LOGOFF ON DATABASE
SET logoff_time = sysdate
WHERE sys_context('USERENV','SESSIONID') = session_id;
That’s it. You can now search the session_audit table for logins durring a time window or all logins for a specific user. You could even check who is using a certain application.
I mentioned one possible issue, that you don’t want the session_audit table to fill up your system tablespace, however it is also important to mention that if your logon trigger fails for some reason people will not be able to log in, so watch the space, no matter where you put it.
Donald Burleson (who desperately needs a new portrait for his website) of Burleson Consulting offers these instructions for a similar trigger, however he is grabbing more information and fills most of it in at the end.
oracle, sql, dba, database administration, database development, database security, database, oracle security