Re: Trapping of Rogue Statement

If using 9i, you can use DBMS_FGA for ³fine-grain auditing².

Another way (for any version) is to search V$SQLTEXT for that phrase in an UPDATE statement, record the hash value of the SQL statement, and then use that hash value to search V$OPEN_CURSOR to find any session IDs (i.e. column SID). From there, you can try to zero in on the code running in that session, perhaps using SQL Tracing (event 10046) to make it spill its guts...

on 9/11/03 10:34 PM, VIVEK_SHARMA at VIVEK_SHARMA_at_infosys.com wrote:

> An unwanted update - del_flg=²Y² is happening while an application is underway
> with thousands of Concurrent Users
>
>
>
> We need to trap & get as much info on this update which is somehow happening
> from somewhere in the application code .
>
>
>
> How as a DBA can we do this?
>
>
>
> Thanks
>
>
>
>  
>
>
>
>
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Tim Gorman
  INET: tim_at_sagelogix.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).