Toad Debugger Breaking

All,

I’m running Toad for Oracle Version 10.1.1.8 and have the debugger
setup to not break on exceptions. Back in Version 9.7 this worked
great. Now in the current version I am getting the debugger breaking
on all exceptions. The only difference I notice between having the
break on exception checkbox checked and not checked is that when
checked, I get an alert stating that an exception was encountered.
When it’s not checked, the debugger doesn’t show the alert, but does
stop at the point of the exception – which is in this case handled.
What do I need to do to get this to not break on all exceptions? Is
there another switch I need to set to get to the behavior I want?


Rumpi Gravenstein

I have some more information. If I select run to cursor, the process
behaves as I would like. When I select step over, exceptions cause a
break to occur.

On Mon, Dec 14, 2009 at 1:57 PM, Rumpi Gravenstein wrote:

All,

I’m running Toad for Oracle Version 10.1.1.8 and have the debugger
setup to not break on exceptions. Back in Version 9.7 this worked
great. Now in the current version I am getting the debugger breaking
on all exceptions. The only difference I notice between having the
break on exception checkbox checked and not checked is that when
checked, I get an alert stating that an exception was encountered.
When it’s not checked, the debugger doesn’t show the alert, but does
stop at the point of the exception – which is in this case handled.
What do I need to do to get this to not break on all exceptions? Is
there another switch I need to set to get to the behavior I want?


Rumpi Gravenstein


Rumpi Gravenstein

bump…

---------- Forwarded message ----------

Rumpi,
I’m not seeing this behavior. What version of Oracle are your running on? Can you create a sample proc that duplicates the issue?

Greg

I see this thread is quite old, but I have this problem too.

TOAD 10.5.0.41
Oracle 10.2.0.5.0

Did you find a fix?

Thanks,
Mark.

I still have this issue. Also, no response from Quest staff beyond a request
for a test case which I provided.

On Mon, May 2, 2011 at 10:39 AM, mark finegan
wrote:

Message from: markf

I see this thread is quite old, but I have this problem too.

TOAD 10.5.0.41
Oracle 10.2.0.5.0

Did you find a fix? 

Thanks,
Mark.

Historical Messages

Author: mark finegan
Date: Mon May 02 07:39:53 PDT 2011
I see this thread is quite old, but I have this problem too.

TOAD 10.5.0.41
Oracle 10.2.0.5.0

Did you find a fix? 

Thanks,
Mark.

__

Author: Rumpi Gravenstein
Date: Tue Dec 29 11:25:49 PST 2009

__

Author: Rumpi Gravenstein
Date: Wed Dec 16 08:07:54 PST 2009

__

Author: Gregory Liss
Date: Wed Dec 16 05:36:27 PST 2009

Rumpi, I’m not seeing this behavior. What version of Oracle are your
running on? Can you create a sample proc that duplicates the issue? Greg

__

Author: Rumpi Gravenstein
Date: Wed Dec 16 05:11:00 PST 2009
bump... ---------- Forwarded message ----------
__

Author: Rumpi Gravenstein
Date: Mon Dec 14 13:26:37 PST 2009
I have some more information. If I select run to cursor, the process behaves
as I would like. When I select step over, exceptions cause a break to occur.
On Mon, Dec 14, 2009 at 1:57 PM, Rumpi Gravenstein wrote: > All, >
> I'm running Toad for Oracle Version 10.1.1.8 and have the debugger
> setup to *not* break on exceptions.  Back in Version 9.7 this worked
> great.  Now in the current version I am getting the debugger breaking
> on all exceptions.  The only difference I notice between having the
> break on exception checkbox checked and not checked is that when >
checked, I get an alert stating that an exception was encountered. > When
it's not checked, the debugger doesn't show the alert, but does >
stop at the point of the exception -- which is in this case handled. >
What do I need to do to get this to not break on all exceptions?  Is >
there another switch I need to set to get to the behavior I want? > >
-- > Rumpi Gravenstein > -- Rumpi Gravenstein
__

Author: Rumpi Gravenstein
Date: Mon Dec 14 10:57:12 PST 2009

All, I’m running Toad for Oracle Version 10.1.1.8 and have the debugger
setup to not break on exceptions. Back in Version 9.7 this worked great.
Now in the current version I am getting the debugger breaking on all
exceptions. The only difference I notice between having the break on
exception checkbox checked and not checked is that when checked, I get an
alert stating that an exception was encountered. When it’s not checked,
the debugger doesn’t show the alert, but does stop at the point of the
exception – which is in this case handled. What do I need to do to get this
to not break on all exceptions? Is there another switch I need to set to get
to the behavior I want? – Rumpi Gravenstein

__
_______________________________________


Rumpi Gravenstein

You might want to open a support case with Quest. This board is informal, so to
expect an answer to every question from a Quest person is a little unreasonable.

If you can provide the test case again, I’d be happy to try your scenario
in v10.6 and v11 – assuming it’s a Toad issue and not an Oracle one.

When I run this program

CREATE PROCEDURE raise_salary ( emp_id NUMBER , amount NUMBER ) AS

curr_sal NUMBER ;

BEGIN

SELECT sal INTO curr_sal FROM emp WHERE empno = emp_id ;

IF curr_sal IS NULL THEN

/* Issue user-defined error message. */

raise_application_error (- 20101 , ‘Salary is missing’ );

ELSE

UPDATE emp SET sal = curr_sal + amount WHERE empno = emp_id ;

END IF;

END raise_salary ;

And run with emp with NULL for salary, it breaks on Exception when the break on
exception option is enabled.

If I toggle that option off, and run again, it runs to completion and I get an
ORA-20101 & ORA-06512

So for me, it works as expected.

This is 11.2.0.1 running Toad v10.6

Jeff