PL/SQL Debugger!

[arun_rs]

When I step in through the debug mode and place the cursor over the variable I have stepped through, the message displayed on the popup says 'Not A Variable'. I am not able to debug. Please help, this is urgent.

 

[Marco Kalter]

Can you let me know your Oracle Server version, and the type of variable you are trying to view (global/local, private/public, scalar/compound)?

Note that the debugger can only display scalar datatypes (varchar2, number, date, ...) or collections of a scalar data type. It cannot display compound datatypes like records or object types.

Also note that Oracle Server 8.0.4 and earlier does not support global package variables (private or public).

Furthermore, if only the specification or body of a package is compiled "with debug information" then this error message can also occur. In that case you can explicitly add debug information by right-clicking on the package in the Object Browser or in a source file, and selecting "Add debug information" from the popup menu.

------------------
Marco Kalter
Allround Automations

 

[arun_rs]

I am Oracle 9i release 2. It is not displaying the value on any variable. It is for scalar datatypes. The same thing I have seen it work before.

 

[Marco Kalter]

Perhaps you can explicitly add debug information by right-clicking on the package in the Object Browser or in a source file, and selecting "Add debug information" from the popup menu?

------------------
Marco Kalter
Allround Automations

 

[pjotr]

I get this error when I step over dynamic code that uses the dbms_sql package. The error occurs exactly when I step over the dbms_sql.execute statement. The really weird thing is that it's not all the variables that end up as "Not a variable", about a third are still ok. And it's always the same variables...

Edit: Seems I was wrong about the dynamic SQL part... I commented the part with the dynamic SQL and got the same error. Now it happens just a few rows down from the previous position... What does this? It makes it rather hard to debug the code when all of a sudden the program decides that 2/3 of the variables are "Not a variable"...
Anyone?..

[This message has been edited by pjotr (edited 12 September 2003).]

 

[pjotr]

Bumping this one, since the edit didn't do it...

 

[ScottMattes]

I sometimes see the same thing under 9.2. Not all the variables, just like you. At one point I noticed that initially entering the package all the vars were displayable, but after 'something' some were and some were not. I was not able to track down when this happens.

------------------
------------
Scott Mattes

 

[Marco Kalter]

I'm not aware of this problem. If it is reproducible, I would love to receive a case that reproduces this.

------------------
Marco Kalter
Allround Automations

 

[pjotr]

It could have something to do with the size of the procedure. The one I'm having trouble with is insanely large, about 3000 lines(!). I removed almost all of the code after where the problem appears and everything worked fine. No more "Not a variable". I'd like to be able to debug without removing 95% of the code, though...

Let me know what information you need.

 

[Marco Kalter]

I will try this with a really big package.

------------------
Marco Kalter
Allround Automations