Page History
...
Table 8-9 Extended Statistics table
Column Description
...
| Column | Description |
|---|---|
| # | Displays the sequential number of the step. |
| Step |
...
| ID | Displays the number of the explain plan step. |
| Step |
...
| Provides a short description of the explain plan step. |
| Rows |
...
| Displays the number of rows returned by this step. |
...
| Time | Displays when the alternative statement was last run. |
...
| Blocks | Displays the total number of blocks in the alternative statement. |
| Executions |
...
| Displays the number of executions of the alternative statement. |
About the History view of resource consumption
The History view displays the resource consumption over time vs. cost, and changes over time. This lets you determine which changes led to performance problems.
...
- Main area
- Change History area
| Info |
|---|
...
If you use the Oracle rule-based Optimizer, cost information is not available. If tables and indexes are not analyzed, statistics changes are not available. |
About the Main area of the History view
The Main area displays resource consumption over time, estimated cost over time, changes over time, and executions over time.
The following views are available in the Main area:
- Overview
- Text
About the overview of history information
The Overview, in the SQL tab, displays the following overtime graphs:
Table 8-10 GraphsGraph Description
| Graph | Description |
|---|---|
| In Oracle (Avg.) |
...
| Illustrates the average resource consumption of the statement over time; does not detail the states or substates. |
...
| Cost | Displays the estimated cost calculated by the Oracle cost-based optimizer over time. This information is generated whenever you explain the statements using Precise for Oracle. |
...
| Changes | Marks significant events that affect the statement and the objects that it accesses over time, namely analyze statistics changes, schema changes, and execution plan changes. The execution plan changes information is generated whenever you explain the statements using Precise for Oracle, either using the PMDB process or the SQL tab. The statistics changes information is generated whenever you run the PMDB process Collect Schema Changes. It scans all the objects referenced by the statement. The schema changes information is generated whenever you run the PMDB process Collect Schema Changes. It scans all the objects referenced by the statement. |
...
See “About the Change History area” on page 143. |
...
| Executions | Displays the number of executions of the selected statement over time. |
About the text of a statement in the History view
The Text view, in the SQL tab, displays the full SQL text of the statement and information on the statement and execution plan, as follows:
Table 8-11 Text view display
Information Description
...
| Information | Description |
|---|---|
| Cabinet | The cabinet where the statement is stored. |
| Folder |
...
| The folder within the cabinet where the statement is stored. |
...
| Origin | The source of the statement. The Precise for Oracle Collector automatically captures most statements when they are executing in Oracle, but you can also import statements from source files or save them manually. A statement can be automatically collected, generated as related SQL, part of a predicted plan in the |
...
What-If tab, entered by users, imported from a source file, or generated as a related SQL by a user. |
| Saved |
...
| on | The date that the statement was saved. |
| Parsing |
...
| Information | Indicates whether Precise for Oracle has performed an extra level of parsing above that performed by Oracle to support more detailed analysis and syntax color highlighting. For statements that are explained in the background, parsing must be enabled in the Explain Statements PMDB process in AdminPoint (see the Precise Administration Guide) for statements that are explaining in the background. For statements that you explain in the SQL tab, parsing must be enabled from Settings>General Settings>SQL. By default, parsing is enabled. Some statements cannot be parsed. See the Precise Administration Guide. See “About SQL settings” on page 27. |
| Explained |
...
| on | The date the latest explain plan was generated. |
...
| Cost | The estimated cost calculated by the Oracle cost-based optimizer. |
| Parsing |
...
| User | In the case of an imported or manually saved statement, the Oracle user that was specified at the time; in the case of an automatically captured statement, the first Oracle user that the Precise for Oracle Collector found running the statement. |
About the Change History area
The Change History area displays the changes that may have affected the performance of the statement over time. Information on the following type of changes is displayed:
...
Table 8-12 All Changes table
Column Description
...
| Column | Description |
|---|---|
 | Switches to the Plan view and displays the first access plan that was created by the Explain Statements process after the specified change was detected. |
 |
...
| If the object that was changed is one of the entities in the Objects tab (table, view, index, or column), this icon will launch the Objects tab with the selected object in context. Also, if the change type is Access Plan Changed, the icon will launch the Compare view with the specified access plan compared to the last access path, as detected by the Explain Statements process. |
...
| Timestamp | Indicates the date that the change was detected. |
| Change |
...
| Type | Displays the type of change detected. Can be one of the following values: |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
■ Different Execution Plan |
Object Indicates the object that was changed, such as table or index.
...