Re: Q:Debug Trigger or where dbms_output.putline

Hi

What I do is to create a logging table and insert into it in the trigger, I also use autonomous transactions to ensure the debug info is not lost on error (depends on the version of course). The other way to do it is to use the utl_file package and open a log file in the same session and close it after you have finished. Again the write to the file will persist as long as the write occurs before any error..:-)

You could also use a PL/SQL debugger, a few tools are available that include a debugger and I think there is a free one from Oracle, search OTN and google. You could also write code yourself using DBMS_DEBUG to debug triggers.

hth

kind regards

Pete

-- 
Pete Finnigan

Email : pete_at_petefinnigan.com
Web site: http://www.petefinnigan.com

Pete is the founder of PeteFinnigan.com Limited a UK based company specialising 
in Oracle security audits and services. Email info_at_petefinnigan.com for details 
and availability.

Pete Finnigan is the  author of the recently published book about Oracle 
security from the SANS  Institute "Oracle security Step-by-step (A survival 
guide for Oracle security)" - see http://store.sans.org for details.

Some recently published articles include:

http://online.securityfocus.com/infocus/1689 - "Introduction to simple Oracle
auditing"

http://online.securityfocus.com/infocus/1644 - "SQL injection and Oracle - part 
one"

http://online.securityfocus.com/infocus/1646 - "SQL injection and Oracle - part 
two"