-
Title
Getting error "profiler tables not found" when using the Hierarchical Profiler -
Description
Getting error "profiler tables not found" when using the Hierarchical Profiler
-
Resolution
Please follow the steps below to setting up the Hierarchical Profiler.
Please note that the hierarchical profiler is different of the standard profiler and other objects must to be installed.
You can set up the hierarchical profiler to run from the Toad schema, or any private user's schema. Each case has a different script to run, as explained in the steps below.Note: The minimum Oracle database version required for the PL/SQL Profiler is Oracle 11g.
The DBMS_HPROF package
Make sure you have the DBMS_HPROF package. If this has not been loaded, please see your Oracle documentation for instructions on where to find it.
Login to Oracle through Toad as SYS.
Make sure that GRANT EXECUTE on the DBMS_HPROF package has been granted to PUBLIC or to the users that will use the profiling feature.
Install Profiler Server Side Objects
There are several database tables and other data structures that are required to use the analyzing functionality of the hierarchical profiler.To install the database objects
Login to Oracle through Toad in the schema where you want the database objects created. These can be created in each individual schema, or alternately, this can be executed in a common schema (such as Toad) and synonyms can be made as described in step 4.
From the Oracle home, RDBMS/ADMIN directory, load the DBMSHPTAB.SQL script into the Editor.
From the SQL Editor menu, select Execute as Script (or press F5).
If you have created them in a common schema, create Synonyms to the following objects and either grant them to each schema requiring them, or make them PUBLIC.
DBMSHP_FUNCTION_INFO (table)
DBMSHP_PARENT_CHILD_INFO (table)
DBMSHP_RUNS (table)
DBMSHP_RUNNUMBER (sequence)
- Check to make sure each schema using the hierarchical profiler has the WRITE privilege on the directory that specified when you start profiling.