If you're using UNIX, I've got a ready-to-run trace package you can have.
You'll have to compile the reader end yourself though (requires Pro*C)
--
Hope this helps
Karl
Certified Oracle DBA
Graham Miller wrote in message <34cf2306.3361959_at_news.u-net.com>...
>"N. Dirks" <ndirks_at_sundn.de> wrote (in <34CE096C.7215_at_sundn.de>)...
>
>| Hi,
>|
>| for an Oracle PL/SQL-Project it would be fine
>| to create sub-transactions within PL/SQL-
>| Methods.
>| These sub-transactions would be responsible
>| for logging method-irregularities (Errors, Exceptions,
>| hurt privileges, etc.) into a special logging-
>| table and commiting these INSERTS without
>| affecting the state of our main-transaction
>| (without COMMIT !!!! on our main-transaction).
>|
>| Is it possible to create a sub-transaction
>| within PL/SQL-Methods ? And how do I create them ?
>|
>| Thanks
>| Nico Dirks
>Hello,
> One way of doing this is to use a 'pipe' to send the messages to a
>'listener' in a separate session. The listener is the only task which
>inserts messages into an error messages table. As the listener is
>running as a separate session, it doesn't effect the main
>transactions.
> I have used this technique successfully in a production environment.
>It is also useful for debugging, since messages from any PL/SQL code
>appear almost instantly. I run my listener in the dbms_job queue so it
>is always available. It is written in PL/SQL and only logs messages to
>a table. (I use version 7.2 of Oracle). It is not difficult to write.
> I have code which i will provide a version of the listener which
>runs on a single Oracle instance. The listener refreshes a 'status'
>table every few minutes so DBA's can see if it alive'. I have provided
>a package providing high-level routines for use in end-user programs.
>
>graham
>
Received on Sun Feb 01 1998 - 00:00:00 CST
