view complete error messages

[joe_brig]

I selected don't show error window from the test window. I only get 1 line of the error in the status bar. How do I turn it back on?

I also only get the status line from the command window when calling a stored procedure that fails. Is this the same setting or another?

 

[Marco Kalter]

You selected "Don't show this message again"? If so, what was the error? For normal parsing ore runtime errors this option is not available.

 

[joe_brig]

When running a test script that fails with an oracle error a popup window asks if you want to show the stack trace window. There is also a check box that says "don't show this again"

I don't remember the exact error, but I don't this it matters, I've seen this before.

How do you reverse that selection?

Also, my command window only show 1 line of any error in the status bar. How do I stop this and have the error message shown on the command window?

 

[whip]

I have a very similar problem. When I recompiled a package, my test window started complaining that the program unit was invalidated (As far as I remember PLSQLDev used to recompile referenced packages automatically without complaining before. Now this does not happen, why?) And offered the option to never show this message again which I selected. Now, whatever runtime error happens in a stored package, the call stack is shown automatically, without a question and I can only see the first line of the full error stack.

Questions:

- Is it correct that selecting that option mentioned above causes showing the call stack automatically (I haven't changed anything else)?
- Where can I set it back to the original behaviour?
- What causes (and how should I avoid) the error message about the package being invalid? Reconnecting is not really an option.

Thanks

 

[Marco Kalter]

As far as I remember PLSQLDev used to recompile referenced packages automatically without complaining before. Now this does not happen, why?

The Oracle Server does this automatically, it is not a PL/SQL Developer thing. All referenced objects must be without compilation errors of course.

Is it correct that selecting that option mentioned above causes showing the call stack automatically (I haven't changed anything else)?

Yes, it will remember the button you chose when you selected this option, and will not show the message again.

Where can I set it back to the original behaviour?

You have to open the user.prefs file in the \Preferences\[name] subdirectory in the PL/SQL Developer directory. This ini file has a [DSA] section with all "don't show again" entries. You can delete the line(s) you want, in this case the line with ViewStackDump=x.

What causes (and how should I avoid) the error message about the package being invalid

My first guess would be a compilation error in a referenced object.

 

[whip]

Originally posted by Marco Kalter:

As far as I remember PLSQLDev used to recompile referenced packages automatically without complaining before. Now this does not happen, why?

The Oracle Server does this automatically, it is not a PL/SQL Developer thing. All referenced objects must be without compilation errors of course.

Yes, all objects were valid, I checked that. What I thought of is that the "existing state" of a package (held in the PGA?) may get invalid if referenced objects are modified. If I remember correctly, this cached invalid state is not refreshed automatically by the Oracle Server.
However, I tried to reproduce the issue with a simple package and did not succeed (yet).

You have to open the user.prefs file in the \Preferences\[name] subdirectory in the PL/SQL Developer directory. This ini file has a [DSA] section with all "don't show again" entries. You can delete the line(s) you want, in this case the line with ViewStackDump=x.

Thanks, that worked.