This is the first issue in 12.1’s known issue list and I need it fixed asap. It has been an issue in one form or another for 5+ years. Could someone investigate this and fix this please.
Kevin,
As you have been told numerous times over the last 5+ years, there is nothing that we can do to fix this issue for you. The issue occurs because the target
session (where the ref cursor results are stored) gets corrupted and is not available when exceptions are thrown. This is an issue with the Oracle DBMS_DEBUG debugger API, not Toad. If you were to build a debug session in SQL*Plus and execute, you would
have the session hang instead of giving no output. Instead of hanging forever and forcing you to restart Toad, we track when the exceptions occur and choose not to attempt to get the ref cursor (or dbms_output) results. Unfortunately, we have no control
over the DBMS_DEBUG API as it belongs to Oracle.
Something you may be surprised to find out is that Oracle’s own SQL Developer (versions 3.2 and 4) product also does not provide you with the ref cursor (or
dbms_output) output (using the SP_TEST5 procedure you sent to us in the past). Their product also does not use the DBMS_DEBUG API but uses JDWP and still fails when trying to debug the code you’ve provided. Given that the manufacturer of the DB doesn’t
support your issue, I’m not sure how you would expect the Toad for Oracle team to.
Greg
From: Kevin Dyer [mailto:bounce-KevinDyer@toadworld.com]
Sent: Tuesday, January 14, 2014 12:03 PM
To: toadoraclebeta@toadworld.com
Subject: [Toad for Oracle - Beta Discussion Forum] No REFCURSOR output if an exception occurs in the debugger
No REFCURSOR output if an exception occurs in the debugger
Thread created by Kevin Dyer
This is the first issue in 12.1’s known issue list and I need it fixed asap. It has been an issue in one form or another for 5+ years. Could someone investigate this and fix this please.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum
Flag
this post as spam/abuse.
Thanks Greg for your response.
This is a MAJOR issue as it, potentially, affects ALL procedures and functions that return ref cursor results. The reason being that results are NEVER returned from ANY procedure or function in which an exception, handled or unhandled, occurs.
This means that to accurately debug ANY procedure or function in which an exception, handled or unhandled, occurs you MUST, also, execute the procedure or function in “No Debugger” mode.
Due to the scale of this problem, I look forward to you/Dell liaising with Oracle and getting this issue highlighted, investigated & resolved.
Oracle announced like 5-6 years ago that the Probe Debugger API is dead - i.e. there will be no fixes or new feature improvements. While they have actually made a few entirely at their discretion, they nonetheless stand behind the general position that Probe API is dead. So there is not going to be any liasing to fix. We have zero leverage on this issue. In fact since Oracle debuted SQL Developer the line “Toad users need” does not play as well as in days past when liasing with Oracle. If users like you on the other hand have any connections or clout with Oracle, then you guys might be able to effect change. Otherwise, posting in caps is not going to accomplish anything. We heard you years ago on this and tried - Oracle is the issue here and we cannot move them. You were not ignored or discounted. It just is not in our power to fix. Sorry.
I’m unsure how to proceed, but thanks Bert for your response.
Greg/Bert,
This issue has now been fixed in Oracle’s SQL Developer 4.0.3.
That said, there is an issue in their “Debug PL/SQL” window where parameters with spaces are not enclosed in quotes, however, this can be corrected and saved for future use.
SQL Developer uses an entirely different debugger than Toad for Oracle (JDWP vs DBMS). Since they haven't fixed the DBMS debugger to follow, there is still nothing on our side to fix your issues.
Greg
On Oct 29, 2014, at 6:43 AM, Kevin Dyer bounce-KevinDyer@toadworld.com wrote:
RE: No REFCURSOR output if an exception occurs in the debugger
Reply by Kevin Dyer
Greg/Bert,
This issue has now been fixed in Oracle's SQL Developer 4.0.3.
That said, there is an issue in their "Debug PL/SQL" window where parameters with spaces are not enclosed in quotes, however, this can be corrected and saved for future use.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.Toad for Oracle - Beta Discussion Forum
Flag
this post as spam/abuse.
