Debugging Test Scripts with 10g

[pribble]

We recently upgraded to 10g and now we are unable to debug or step into a test script.

Is this no longer valid with 10g? We are able to accomplish this with compiled procedures and packages.

 

[LMW]

Hello,

maybe system privilege DEBUG CONNECT SESSION is missing which is mandatory when using oracle 10g.

LMW

 

[Marco Kalter]

An additional requirement in 10g is that the program unit must be compile "with debug information". There are 2 ways to accomplish this:

1. Enable the Debugger preference "Add debug information when compiling". Now you don't have to worry about debug information anymore, as each compilation implicitly adds it.
2. Right-click on the program unit in the Object Browser and select "Add debug information".

The debug information goes away if you compile it without the "add debug information when compiling" preference, or when someone else compiles it without debug info.

 

[pribble]

Are you saying that you can no longer step thru code in the test window if it is not compiled?

 

[Marco Kalter]

In 10g that is indeed not possible. As a workaround you can create a simple "debug" stored procedure that can act as a placeholder for the anonymous PL/SQL that you want to debug, and create a standard test script to run it. This way you can make the process a little bit more efficient.