Removing PL/SQL Debug Information

[Frontline]

In both the current (V6) and Beta (V7) PL/SQL Developer products it is possible to add debug information to a PL/SQL Package. Is it possible to remove the debug information using PL/SQL developer as I can't seem to untick the add debug information option.

Any help gratefully appreciated.

 

[Marco Kalter]

Why do you want to do that?

 

[William Robertson]

Perhaps the package was compiled with debug by mistake, or perhaps he has finished debugging it, or doesn't want subsequent debug sessions to step through it each time?

Try:
ALTER PACKAGE packagename COMPILE;

 

[Frontline]

First of all many thanks for the replies.

Why I want to remove debug is to improve performance and debugging is no longer required as the package is in production.

I appreciate that you can manually recompile the package but I wanted to do this from the tool - which I can't seem to do. Is this a "feature" of PL/SQL developer or am I missing something?

Any more help gratefully appreciated.

 

[William Robertson]

You could write your own "compile without debug" using Browser Extender, but that does rather duplicate the existing "Recompile" and "Add debug information" functionality. I was half expecting "Recompile" to just issue an "ALTER PACKAGE ... COMPILE" and thus remove debug, but it doesn't. Perhaps it could ask you whether to retain debug, when present?

 

[Joachim Rupik]

It depends on "Preferences/Oracle/Debugger/Add debug information when compiling" preference.

 

[Frontline]

Many Thanks for the above info...

Would be nice as a change request to simply be able to "untick" the add compile info option though.

 

[William Robertson]

Originally posted by Joachim Rupik:
It depends on "Preferences/Oracle/Debugger/Add debug information when compiling" preference.

I don't see how those preferences help you remove debug info from an object that currently has it. Am I missing something?

 

[Joachim Rupik]

If is unchecked a 'Recompile' popup menu item issues 'ALTER COMPILE', when is checked 'ALTER COMPILE DEBUG'. So (re)compiling without adding debug information simply removes debug info.
When this preference is checked 'Recompile' and 'Add debug information' popup menu items do the same.
Also a checkmark of the 'Add debug information' popup menu item shows if object already contains debug information.

 

[Marco van der Linden]

Slightly off-topic, but one of the (very) few things I like about that Froggy developer tool is that you can see that debug information was added to the code from the icon (some sort of bug) rather than having to open the context menu. But apart from that.......PLSQLDev rocks!

 

[Marco Kalter]

Note that there are no performance consequences from adding debug information. It is just symbol information, and the actual PL/SQL code is not affected at all.

 

[Kirurgs]

Well, there are performance consequences actually
The thing is that when debug info is added, package execution takes a lot more memory to process, and so cpu as well, however queries takes usual time to process...
Unfortenately this is not just plain theory

 

[Marco Kalter]

I tried this, but don't measure any differences.

You can use the Browser Extender Plug-In to create a "Remove debug information" option. All you need to execute is "alter compile" or, in case of a package body, "alter package compile body".