can't compile package

[ScottMattes]

I am using PLSD 5.1.2.687 on Oracle 9i Enterprise Edition 9.2.0.3.0 using OCi ver 8.0

Suddenly when I compile a certain package (others that I have tried work OK) i get 'compiled with warnings', but no warnings are being displayed.

If I open a command window and paste the spec and body to it the compile is successful. This is nice, but I can't run with break points in the test window because of this (or so it seems, when i put the cursor over a var during the run it reports 'no debug info').

I have tried shutting the PC completely down and powering off/on, but the problem continues.

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

 

[ScottMattes]

Well, I don't know what I did to change this, but now at least I can debug and see variable values.

Still, the compile says 'with warnings' but no warnings are shown and if I compile in a command window no warning about warnings comes up.

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

 

[Marco Kalter]

Can you send me a screenshot of this problem by e-mail?

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

 

[ScottMattes]

Originally posted by mkalter:
Can you send me a screenshot of this problem by e-mail?

Sorry, I cannot (customer requirements). When I compile the package the only thing that changes is the status bar and the change is a message that there were warnings.

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

 

[ScottMattes]

Originally posted by ScottMattes:
Sorry, I cannot (customer requirements). When I compile the package the only thing that changes is the status bar and the change is a message that there were warnings.

My bad! Sort of. I don't know what I was thinking, but the 'compiled with warnings' seems to mean the the 'hint' about a var value not being used in a proc that I see.

What started all this was when I tried debugging after getting this and a variable came up as 'not a variable' when I hovered the mouse over it. I am debugging that package now and I am finding that about half the variables are coming up as 'not a variable' - even if I just saw a line assign a value to it!

I went to the top of the proc and hovered over the variables defined there one by one and some would show values and some would be 'not a variable', then some would show values and some weren't vars and some more would show values, etc, etc, etc. It didn't seem to matter whether they were CHAR, VARCHAR2, DATE, really large fields or small fields.

Any ideas about this?

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

 

[ScottMattes]

And, to muddle matters, if I check the variables as the unit is just getting started all the variables show a value, it is only after they are reset (I think) that they then become 'not a variable'.

Strange.

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

 

[Marco Kalter]

The "Not a variable" message can imply the following:

1. You are debugging a package, and only the spec or body are compiled "with debug information". To fix this, right-click on the package and select "Add debug information". Note that the debug information is removed if the package spec or body is compiled without the "Add debug information when compiling" debugger preference.

2. The variable is not a scalar variable.

3. The Oracle Debug API of your Oracle Server version does not support the specific variable type. For example: The Debug API of Oracle 7.3 does not support global (private or public) package variables.

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