How do you use trace/profiler?

[oneworld95]

I've got PL/SQL Developer 6 and have an Oracle 9i procedure that takes about 30 seconds to run. How do I use the tool to determine where the bottlenecks are in the queries? Thank you.

 

[ScottMattes]

The short answer:

fire up PLSD, right click on the procedure and select Test, in the Test window click on the Profiler button and then on the debug button. After the run is done click on the Profile tab to view the results

Note:
DBMS_Profiler package has to be available to the schema that you run this on. The package/proc/func has to be compiled with debug and maybe other things I'm not aware of since I run on a private DB as a privileged user.

 

[rbrooker]

hi,

you dont actually click the debug button, this will turn the profiler off. click the cog icon on the toolbar, or press F8 ( if not differently configured )

 

[ScottMattes]

My mistake.

It gives an error msg about not being able to do a profile while doing debug.

 

[NK]

you dont actually click the debug button, this will turn the profiler off. click the cog icon on the toolbar, or press F8 ( if not differently configured )

Thanks! Your reply (from almost 3 years ago!) solved the problem I was having today with PLSD 7.1.5.

If I was in debug mode, I click on the "Create Profiler report", and I click F9 to start running the procedure, I get "Profiler not supported in debug mode, report will not be created".

If I revoke debug privilege so that I will not be in debug mode, I get "ORA-0131: Insufficient privileges" when I use F9 to start running the procedure.

Maybe the PLSD GUI interface to run code under the Profiler needs to be changed so that people will use F8 and not F9.