PL/SQL Debugger in executing mode forever

[Krishnakc]

Hello:

Could you please assist me with this problem that I have with PL/SQL developer debugger. I am using Version 9.0.6.1665 Windows 7 (64-bit) 6.1 Build 7601 (Service Pack 1).
The debugger works well with 11g Windows Oracle server hosted packages.
However, we recently moved to 12c Oracle Exadata servers and the debugger has issues in working there.
When debugger is fired up, it gets to an executing.. mode and does not show the icons to debug or move forward. I made sure the user has DEBUG ANY PROCEDURE DEBUG CONNECT SESSION. I was told that I had to upgrade to 12c client at my end to see the difference. I upgraded the client from 11g to 12c, yet it made no difference. I right clicked the package and 'added debug information'.

Kindly help if you seen this situation before. I can add more information if you require to resolve this problem.

 

[Marco Kalter]

Can you try the same with the current PL/SQL Developer 12.0 release? You can download the trial version and install it next to your 9.0 version.

 

[Krishnakc]

Thanks, Marco for taking time to respond. I have organizational constraints to install any new software. I am going to try it.

Thanks, again. I appreciate your help. I will let you know if I am able to get the success.

 

[IvanZ]

Exadata most likely means RAC.

Debugging on RAC has a restriction - you must debug on the same instance you're running the code. So TNS should have a specific instance in declaration.

Check it out.

 

[Krishnakc]

Hello Ivan:
Yes, It is on RAC. I am going to check your suggestion with the DBAs. We have TNS and there we got a specific instance defined.

 

[Krishnakc]

Hello Marko, I have 12 version installed and I have no success in debugging yet. The same code is working Toad debugger with the same user id. The version of Toad is 12 again. I am wondering if I need to enable any property in PL/SQL developer.

Krishna

 

[Krishnakc]

Hello Marko:
Could you let me know what could the problem be in this case?

 

[Marco Kalter]

The Oracle Debug API (sys.dbms_debug) internally uses dbms_pipe messages to communicate between the controlling session and the debug session, which apparently can fail on RAC systems. The only workaround is to modify the tnsnames.ora file to connect to only 1 node of the cluster without load balancing and failover.

 

[Krishnakc]

Hello Marco
Thanks for taking time and responding.
Tnsnames.ora is connecting to one node already.

I figured out the workaround(or solution) for this. I had to enable 'background compilation' in preferences under program window and also start the program by passing a DebugSQL parameter. Doing this resolved this problem.
I thank you and Ivan for your time on this.

Krishna

 

[IvanZ]

Check it out in the new 12.0.8 PLD build.

 

[datadeconline]

Hi Marco

Any news about 12.0.8 PLD build ?
About use of DBMS_DEBUG_JDWP ?

Regards
PGuti