OraFAQ Forum: Client Tools » Unable to debug procedure using pl/sql debugger using 10g (Merged 4)

Home » Other » Client Tools » Unable to debug procedure using pl/sql debugger using 10g (Merged 4)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Unable to debug procedure using pl/sql debugger using 10g (Merged 4) [message #387959]

Sun, 22 February 2009 12:26

palanisvr
Messages: 21
Registered: March 2007

Junior Member

Hi all,
when i am trying to debug a procedure by using pl.sql developer 7.15 on oracle 10g
it is automatically getting closed.
Please let me know if you have any solution on this.

Report message to a moderator

Re: Unable to debug procedure using pl/sql debugger using 10g [message #387963 is a reply to message #387959]

Sun, 22 February 2009 12:32

ThomasG
Messages: 3212
Registered: April 2005
Location: Heilbronn, Germany

Senior Member

Based on the fact that you can't seem to control your mouse, I say stop twitching your finger over the "close" button the way you twitch on the "Submit Reply" button.

Report message to a moderator

Re: Unable to debug procedure using pl/sql debugger using 10g (Merged 4) [message #387964 is a reply to message #387959]

Sun, 22 February 2009 12:35

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

Please respond to last post started by you in
http://www.orafaq.com/forum/m/387941/136107/#msg_387941

Report message to a moderator

Re: Unable to debug procedure using pl/sql debugger using 10g [message #387966 is a reply to message #387963]

Sun, 22 February 2009 12:45

Michel Cadot
Messages: 68775
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

ThomasG wrote on Sun, 22 February 2009 19:32

Based on the fact that you can't seem to control your mouse, I say stop twitching your finger over the "close" button the way you twitch on the "Submit Reply" button.

@palanisvr,
Still waiting for an answer in the topic pointed by BlackSwan.

Regards
Michel

Report message to a moderator

Re: Unable to debug procedure using pl/sql debugger using 10g [message #393407 is a reply to message #387966]

Sun, 22 March 2009 11:56

daniel.ivanov
Messages: 2
Registered: March 2009

Junior Member

Hi all!
I'm new in this forum, but pretty old in working with Oracle databases (as user).
Now I'm programming in PL/SQL Developer (version 7.0.1.1066) and I have the following problem: cannot see the value of variables in debugging mode (see attached file)
Oracle version: Enterprise Edition 9.0.2.6.0, Windows XP SP3

Attachment: pl_sql1.JPG
(Size: 63.14KB, Downloaded 1244 times)

Report message to a moderator

Re: Unable to debug procedure using pl/sql debugger using 10g (Merged 4) [message #393408 is a reply to message #387959]

Sun, 22 March 2009 12:08

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

> cannot see the value of variables in debugging mode (see attached file)
Specifically BOOLEAN variables.
I can't say I have ever tried this, but my reading of the manual
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/datatypes.htm#sthref778
leads me to conclude that you have expected behavior.
Just accept BOOLEAN value(s) can not be displayed & move on.

You need to help us by following the Posting Guidelines as stated below.
http://www.orafaq.com/forum/t/88153/0/

Report message to a moderator

Re: Unable to debug procedure using pl/sql debugger using 10g (Merged 4) [message #393409 is a reply to message #393408]

Sun, 22 March 2009 12:35

daniel.ivanov
Messages: 2
Registered: March 2009

Junior Member

Thank you for your answer.
Ok, maybe I've choosen an boolean variable, but the same is happening with varchar or integer variables Confused

Thanks
Daniel

Attachment: pl_sql2.JPG
(Size: 63.44KB, Downloaded 1215 times)

Report message to a moderator

Previous Topic:	Development Tools (3 posts merged by bb)
Next Topic:	[TOAD 9.1] How to "set define off"

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Feb 20 02:07:32 CST 2026