8i | 9i | 10g | 11g | 12c | 13c | 18c | 19c | Misc | PL/SQL | SQL | RAC | WebLogic | Linux

Home » Misc » Here

Comments for DBMS_PROFILER


Subash said...

Good Job Tim, you have conveyed how to use it. The reader can then take off and use the respective functions and variants.

tibbu said...

i did exactly as you said but for me when i run the procedure to start and stop profiler, it says

identifier 'do_something' must be declared.

what to do ?

Tim... said...

Hi.

"do_something" is the name of the procedure I create in the article. It is the procedure I'm tracing. If you want to practice the tracing, you must create this procedure also.

If you are tracing your own code, then don;t call "do_something", call your own code instead.

Cheers

Tim...

TIBBU said...

hi Tim, i i created procedure in other schema. that is why i was getting error. now i created proc in the same schema where iam running the profiler.

it runs now. but it didnot insert any records in the profiler tables.

why is that?

and also in my TOAD, profiler is disabled.
what should i do to enable it??

i have grant on the pkg dbms_profiler also

tibbu said...

FYI

my TOAD version is 9.6.1

Tim... said...

Hi.

You should do the profiling and query the tables from the user that owns the procedure.

Please ask technical questions in the forums, not here.

Cheers

Tim...

Santhosh Jose said...

@Tim - Would these steps hold good in SQLDeveloper as well? Especially step 4. Reason I ask is when I tried to profile a package, the package doesn't get picked up in the "units" table (only the anonymous block does). Compiling the package in debug mode fixed the issue. Just wondering if this was due to SQLDeveloper or maybe a required step in the latest database versions.

Tim... said...

Hi.

SQL Developer has built in profiler functionality, that uses this package under the hood. If you are using SQL Developer, it's best to stick with that, rather than using the package manually.

Cheers

Tim...

DO NOT ask technical questions here! They will be deleted!

These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!

If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.