RE: Toad Debugger

"Simoneau, Roger" <[email protected]>
Newsgroups gmane.comp.db.oracle.toad.free
Message-ID <85214F3A9C2FE94F9FF1D7C6456E33F9042D76441D@EX-CLUS-MBX-01.abcp.ab.bluecross.ca>
>> I need to be able to just run the
>> debugger daily whenever I need it.

Caveat: I'm not a DBA, I haven't specifically stepped through what's required to activate debugging.

The first thing to remember is that Toad is nothing more than a pretty GUI that accesses Oracle functionality.  So the access to be able to debug is not a "Toad thing".  It's an "Oracle thing".  You'd have to set it up even if you wanted to debug through SQL Plus.

From the Oracle documentation (which one could easily Google) there is a new privilege model starting with the Oracle 10g Database.  Herein lies the importance of having overlooked which database version you are running on.  A quick summary of access required specific to 10g release 1:

DEBUG CONNECT SESSION (system privilege a person must have to execute debug)
DEBUG and EXECUTE privileges (I think this is directly related to the stored code)

The above allows you - as I understand it - to run the command:

Alter package <package name> compile debug;

A command Toad handles for you.  And you should be off and running.

Again: this is for 10g release 1.  Your DBA really should review the appropriate Oracle documentation to understand what's needed for your specific database.

For example:

DEBUG ANY PROCEDURE <- this should never be granted to a developer!  My humble opinion as a developer.

JAVADEBUGPRIV <- carries the role above, very dangerous.  As the Oracle doc says:


"Granting DEBUG ANY PROCEDURE privilege, or granting DEBUG privilege on any object owned by SYS, means granting complete rights to the database."
Very bad to do, yup!

Roger S.

________________________________
This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.