Re: Q:Debug Trigger or where dbms_output.putline

From: Carsten Saager <carsten_at_saager.org>
Date: Sat, 31 May 2003 19:55:34 +0200
Message-ID: <bbaqc5$7jeei$1@ID-74580.news.dfncis.de>

"Ralf Bender" <ralf.bender_at_arcor.de> schrieb im Newsbeitrag news:oprpz3m4n8r3iuw7_at_news.arcor.de...
>
> Hi
>
> is there someone who can tell a good way to debug a trigger? ...
Have you tried JDWP with JDeveloper 9.0.3?

This allows you to perform source-level-debugging of any code executed in the database. I am not sure if it available for servers prior to 9.2

The setup is very easy:

- Setup a Database Connection to the debuggee's instance
- Recompile the PL/SQL and Java units (this generates debug-information)
- Create an empty Project in JDev
- Set the Debugging (Remote) properties to "Listen to JDPA" and choose the

connection created above in the dropdown-list - Start Debugging of the Project, a small window will popup and ask you for a port number (default 4000)

Your application has nathing more to do than to call dbms_debug_jdwp.connect_tcp('name-of
the-machine.running.the.jdeveloper',4000); and now the session is connected to your Jdeveloper instance!

To stop Debugging simply call dbms_debug_jdwp.disconnect().

If think the oracle-user of the debuggee and of the connection in Jdev must match. SYS has to grant him JAVADEBUGPRIV at least for debugging Java code.

ciao

    Carsten Received on Sat May 31 2003 - 12:55:34 CDT