SQL Details (Full Screen) Page
To open the SQL Details (full screen) page
-
Select the Spotlight on Oracle connection in the Spotlight Browser.
-
Click I/O | SQL Page.
- Select a SQL Statement in the Top SQL grid.
- From any of the sub pages click Full Screen.
- Click SQL Details
Note: Click Restore screen to return to the Top SQL grid.
SQL Details
| Data | Description |
|---|---|
|
SQL ID |
The SQL identifier for the specified SQL statement in the library cache. |
|
Address |
The address of the cursor that contains the SQL statement. |
|
First Load Time |
The first time the SQL statement was loaded. |
|
Last Active Time |
The last time the query plan for the SQL statement was active. |
|
Optimizer Mode |
The mode under which the SQL statement was executed. |
|
Command Type |
The Oracle command type (2, for example, represents an INSERT command). |
|
Service |
The name used to connect to the Oracle instance. |
|
Module |
The name of the module (if any) being executed when the SQL statement was first parsed. |
|
Child Number |
The number of the cursor (if any) that is a child of the cursor that contains the SQL statement. |
|
Hash Value |
The hash value for the SQL statement in the library cache. |
|
Last Load Time |
The last time the SQL statement was loaded. |
|
Parsing Schema Name |
The schema name that was used to build the child cursor. |
|
Object Status |
The status of the cursor. |
|
Outline Category |
The category (if any) of the outline applied during construction of the cursor. |
|
Action |
The name of the action being executed when the SQL statement was first parsed. |
SQL Text
The full text of the SQL statement being executed.
|
Action |
Description |
|---|---|
Click Explain SQL  |
Explain the SQL via the Explain Plan. Tools | Explain Plan |
Click SQL Optimizer  |
Display context-sensitive tuning advice for SQL statements via SQL Optimizer (or SQL Tuning). Tools | SQL Optimizer Note: For more information on SQL Optimizer, see the SQL Optimizer documentation. |
Click Predictive Diagnostics  |
Will the selected SQL statement scale adequately as data volumes and SQL execution rates increase? View Spotlight's Predictive Diagnostics analysis. SQL Performance |
| Right-click the SQL Text window and select Format SQL. | Display the SQL statement in a more readable form. |
Note: If the SQL cannot be explained, the Explain Plan and SQL Optimizer (SQL Tuning) options may be unavailable.
SQL Time Breakdown (Grid)
SQL Time Breakdown displays statistical information about the selected SQL statement, including execution statistics and a breakdown of the time spent processing the statement. SQL statistics may be used to identify where the SQL statement can be tuned to use system resources more efficiently.
| Column | Description |
|---|---|
|
Category |
Each row in the table investigates a specified statistical category. |
|
Value |
The value of the statistic the last time the Top SQL page was refreshed. |
|
Per Exec |
In execution statistics, the value of the statistic per execution of the SQL statement. |
|
Per Row |
In execution statistics, the value of the statistic per row retrieved. |
|
Pct Elapsed |
Within the total elapsed time, the percentage of time spent in each stage of processing. |
| Big Category |
Time Breakdown (ms) - Chart
Time Breakdown (ms) displays the elapsed time spent in each stage of processing, and may show where the SQL statement can be tuned for greater efficiency. The stages displayed include:
- Application
- Cluster
- Concurrency
- CPU
- I/O
- Java
- PL/SQL
- Other
If the amount of time spent in Java or PL/SQL processing is significant, examine the application that is responsible for originating the Java or PL/SQL processing.