Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Trigger not firing!!!!!!!!!!(URGENT)

RE: Trigger not firing!!!!!!!!!!(URGENT)

From: Jesse, Rich <Rich.Jesse_at_quadtechworld.com>
Date: Thu, 9 Jun 2005 08:53:47 -0500
Message-ID: <FB5D3CCFCECC2948B5DCF4CABDBE66971FF9F6@QTEX1.qg.com>


Hi Dimitre,

Some programs may auto-commit or auto-rollback on disconnect. Check a 10046 trace to see where the COMMIT happens. The row stays, so logically it must happen somewhere in the connection, right?

Oooh, a LOGON trigger for a 10046 trace! :)

Rich

-----Original Message-----
From: Radoulov, Dimitre [mailto:cichomitiko_at_gmail.com]=20 Sent: Thursday, June 09, 2005 8:38 AM
To: Jesse, Rich; oracle-l_at_freelists.org
Subject: Re: Trigger not firing!!!!!!!!!!(URGENT)

> 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?

Why do you think that only the sqlplus's sessions will be logged?

Regards
Dimitre Radoulov

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jun 09 2005 - 09:58:56 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US