We just saw tracing capabilities in PL/SQL programs. It presents the execution flow of the program in an interactive format with clear comments at each stage. But it doesn't provide the execution statistics of the program which prevents the user from determining the performance of a program. The user never comes to know about the time consumed at each step or process.
Before the release of Oracle 11g, DBMS_PROFILER was used as the primary tool for profiling PL/SQL programs.
Oracle introduced the PL/SQL hierarchical profiler in Oracle 11g release 1. The profiling was restructured as hierarchical profiling. The hierarchical profiling could profile even the subprogram calls made in the PL/SQL code. It fills the gap between tracing loopholes and the expectations of performance tracing. The hierarchical profiler creates the dynamic execution profile of a PL/SQL program. The efficiencies of the hierarchical profiler...