RE: Trigger not firing!!!!!!!!!!(URGENT)
- From: "Jesse, Rich" <Rich.Jesse@xxxxxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 9 Jun 2005 08:53:47 -0500
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@xxxxxxxxx]=20
Sent: Thursday, June 09, 2005 8:38 AM
To: Jesse, Rich; oracle-l@xxxxxxxxxxxxx
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
--
//www.freelists.org/webpage/oracle-l
Other related posts:
