That's fine, but: 1) What version of Oracle? 2) Where does the 10046 trace say the COMMIT happens? 3) Wouldn't it be "better" if a procedure with a PRAGMA AUTONOMOUS_TRANSACTION were called to do this, including the obligitory COMMIT, thereby helping ensure that all connections (not just from the SQL*Plus program) are logged? My $.02, Rich -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Radoulov, Dimitre Sent: Thursday, June 09, 2005 7:17 AM To: onkarnath.tiwary@xxxxxxxxx; rjamya; oracle-l@xxxxxxxxxxxxx Subject: Re: Trigger not firing!!!!!!!!!!(URGENT) Check this: 14:15:12 SQL> CREATE TABLE log_info (login_date DATE, ipadds=20 VARCHAR2(20),username VARCHAR2(30)); Table created. Elapsed: 00:00:01.10 14:15:17 SQL> grant select on log_info to test; Grant succeeded. Elapsed: 00:00:00.07 14:15:25 SQL> CREATE OR REPLACE TRIGGER logon_audit AFTER LOGON ON DATABASE 14:15:30 2 BEGIN 14:15:30 3 insert into sys.log_info=20 values(sysdate,ora_client_ip_address,ora_login_user); 14:15:30 4 END; 14:15:30 5 / Trigger created. Elapsed: 00:00:00.19 14:15:30 SQL> select * from sys.log_info; no rows selected Elapsed: 00:00:00.00 14:15:40 SQL> conn test/test Connected. 14:15:44 SQL> select * from sys.log_info; LOGIN_DAT IPADDS USERNAME --------- -------------------- ------------------------------ 09-JUN-05 TEST Elapsed: 00:00:00.00 14:15:47 SQL> conn test/test@dbarepo1 Connected. 14:15:53 SQL> select * from sys.log_info; LOGIN_DAT IPADDS USERNAME --------- -------------------- ------------------------------ 09-JUN-05 TEST 09-JUN-05 10.44.19.31 TEST Elapsed: 00:00:00.01 14:15:55 SQL> If get the IP if you use the listener. Cheers Dimitre Radoulov -- http://www.freelists.org/webpage/oracle-l