Page History
This section includes the following topics:
- About the Oracle Findings view
- About Instance findings
- About Activity tab findings
- About SQL tab findings
- About Object Findings
| Anchor | ||||
|---|---|---|---|---|
|
The Findings view displays recommendations that can be used to create a better execution plan and improve the performance of a statement. The Findings vary according to the type of operation in a statement, the Precise product and the technology.
...
- Identify the finding with the highest severity ranking in the Findings table.
- Select the finding type to view additional information on the selected type of operation.
- Read the Highlights and What to do next areas for the finding.
- After you have studied all of the information provided, read the Advice area and perform the recommendation that best suits your needs.
- Follow up on performance to verify that the problem was resolved.
| Anchor | ||||
|---|---|---|---|---|
|
Several Dashboard tab findings exist in the table to help the user. The Dashboard tab for an instance has the following findings:
...
■ Instance-related wait (such as: internal lock wait, shared pool wait, and redo log wait). In this case, switch to the Statistics tab and examine the breakdown of this state in Oracle events.
| Anchor | ||||
|---|---|---|---|---|
|
Several Activity tab findings exist in the table to help the user. These findings are available in Service Caller and Web
...
■ Check the Binds tab for possible offensive values resulting in differing execution plans and performance.
| Anchor | ||||
|---|---|---|---|---|
|
Several SQL tab findings exist to help the user. The SQL tab has the following findings:
...
Advice To avoid a Cartesian Join verify that you have provided the proper Join conditions in the statement's WHERE clause.
| Anchor | ||||
|---|---|---|---|---|
|
Several Object tab findings exist to help the user. The Objects tab includes the following findings:
...