Re: compile debug overhead

Hi,

The DEBUG option allows PL/SQL information to be generated during code recompilation. There is an overhead as a result of that.

Debug option generally speaking evolves overhead and should be used mainly for Code Error Trapping and Code Generation operations.

Regards

"The Views expressed here are my own and not necessarily those of Oracle Corporation"

"Manfred Bauer" <Manfred.Bauer_at_masgmbh.com> wrote in message news:3881F200.ED32393A_at_masgmbh.com...
> Hi all,
>
> we are planning to intoduce the PL/SQL-Debugger XPeditor SQL from
> Compuware.
> During the demonstration of the product, the technician of Compuware
> told us, that
> in order to debug any stored procedure on a Oracle 7 database, you must
> compile the stored procedure with debug option.
>
> alter procedure xyz compile debug.
>
> But when you do this all stored objects, which depend on this stored
> procedure get invalid. So you cannot do this on a production database.
>
> So our solution is to compile all stored objects, that means all
> triggers, functions, prodedures and packages with the debug option after
>
> the installation of the database user.
>
> Can someone tell me, what is the overhead of this method?
>
> With regards
>
> Manfred Bauer
>
>
Received on Sun Jan 16 2000 - 11:55:54 CST