Title: RE: RE: Advance Oracle Trigger Writing Advice
Hi Hannah,
I think you could use a simpler feature to brute-force a trace of your trigger's execution path. The SYS.DBMS_SYSTEM.KSDWRT procedure provides output facilities for the alert.log and session trace
ECTED]@SUNGARD On Behalf Of "Stephane
>Faroult"<[EMAIL PROTECTED]>
> Sent: Tuesday, June 18, 2002 6:48 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: RE: Advance Oracle Trigger Writing Advice
>
> Hanna,
>
>I still have a fairly confus
Hanna,
I still have a fairly confused view of what your problem is and how you plan to
solve it. Jean is right about the solution - autonomous transactions are the easier
way (dbms_pipe is the other one) to ensure that you will not lose any track of your
debugging information even if the tr
