SQLStatistics in AWR

TOPSQL that records the total execution time (note that the total execution time of the SQL statement within the monitoring range, rather than the execution time of a single SQL statement (ElapsedTimeCPUTime + Wait)

Top SQL statements that record the total execution Time (note the total execution Time of the SQL statement within the monitoring range, rather than the execution Time of a single SQL statement. Elapsed Time = CPU Time + Wait

1 SQL ordered by Elapsed Time
Top SQL statements that record the total execution Time (note that the total execution Time of the SQL statement within the monitoring range, rather than the execution Time of a single SQL statement Elapsed Time = CPU Time + Wait Time ).
Elapsed Time (S): the total duration of SQL statement execution. This sorting is performed according to this field. Note that this time is not the time for running a single SQL statement, but the total time of the number of SQL statements executed within the monitoring range. Unit: seconds. Elapsed Time = CPU Time + Wait Time
CPU Time (s): The total CPU usage Time during SQL statement execution. This Time is less than or equal to the Elapsed Time. Unit: seconds.
Executions: Total number of SQL statement Executions within the monitoring range.
Elap per Exec (s): average time for executing an SQL statement. Unit: seconds.
% Total DB Time: the percentage of Elapsed Time of SQL to the Total Time of the database.
SQL id: ID of the SQL statement. Click it to navigate to the SQL details list below. Click IE to return to the current SQL ID.
SQL Module: shows how the SQL statement is connected to the database for execution. If the SQL * Plus or PL/SQL link is used, someone is debugging the program. Generally, the SQL statement that is linked to the foreground application is empty.
SQL Text: A simple SQL prompt. For details, click the SQL ID.

2 SQL ordered by CPU Time:
The top SQL statements with the longest execution time as the sum of CPU time are recorded (note that the execution time of this SQL statement is the sum of CPU time in the monitoring range, rather than the execution time of a single SQL statement ).

3 SQL ordered by Gets:
The top SQL statements whose execution accounts for the total buffer gets (logical IO) are recorded (note that the execution of this SQL statement accounts for the total Gets within the monitoring scope, rather than the Gets occupied by a single SQL Execution ).

4 SQL ordered by Reads:
The top SQL statements that occupy the total Disk Physical reads (physical IO) are recorded (note that the execution of this SQL statement accounts for the total Disk Physical reads within the monitoring scope, instead of the Disk Physical reads occupied by a single SQL Execution ).

5 SQL ordered by Executions:
The top SQL statements sorted by the number of SQL executions are recorded. This sorting shows the number of SQL executions within the monitoring range.

6 SQL ordered by Parse cballs:
Top SQL that records the number of soft resolutions of SQL statements. When it comes to soft parsing (soft prase) and hard parsing (hard prase), it is not worth mentioning the Oracle SQL processing process.

7 SQL ordered by Sharable Memory:
Records top SQL statements that occupy the size of library cache. Sharable Mem (B): the size of the library cache in bytes.

8 SQL ordered by Version Count:
Records top SQL statements for opening sub-game targets.

9 SQL ordered by Cluster Wait Time:
Top SQL statements that record the cluster wait time