retrieving the location of a database trigger call..


Hi - in a 10g Oracle 'Before Insert or Update' trigger is there any
way of find the source of the insert/update...? That is, the name of
any background process, SQL*Plus script or form which may have done
the insert/update..?

If such information isn't lost I'd like to try and use it as a
condition within the trigger but can't see any way of retrieving it.

many thanks, nigel

.

Relevant Pages

  • [NEWS] Multiple Vulnerabilities in Oracle Database (Trigger, Extproc, Wrapped Procedures, PL/SQL Inj
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Multiple vulnerabilities were discovered in the Oracle database server. ... Oracle Trigger Abuse ... written in PL/SQL and execute with the privileges of the definer/owner. ...
    (Securiteam)
  • RE: Access Append Query to update Sequence Generator in Oracle
    ... Jerry Whittle, Microsoft Access MVP ... to be a Trigger for TASSIGNINTERVAL ... Also committing should not make any difference to the sequence or trigger. ... was that the Sequence Generator in Oracle remained at the last number PRIOR ...
    (microsoft.public.access.queries)
  • Re: Help for an Oracle Newbie
    ... application I wrote using SQL Server ported over to Oracle. ... Obviously there are several built in data types in SQL Server that do ... Of course I had to use a different name for the trigger under each ... In SQL Server I always create a CreatedDate column ...
    (comp.databases.oracle.server)
  • Re: Help for an Oracle Newbie
    ... application I wrote using SQL Server ported over to Oracle. ... Obviously there are several built in data types in SQL Server that do ... Of course I had to use a different name for the trigger under each ...
    (comp.databases.oracle.server)
  • Re: Before Insert Trigger
    ... I was running this on Oracle 9.2.0.5 on HP UNIX 11i. ... I have set up a trigger ... >> including unique constraint violation in the trigger. ... > for performance reasons as well as technical ...
    (comp.databases.oracle.server)