Page History

...

The All Changes view displays a list of all changes made. The changes can be statistics changes, schema changes, and execution plan changes. If there are many changes, you may want to use one of the other change types or filter your search using the More... option. See “Associating Associating entities with data that meets specific criteria” on page 30criteria.

The following table describes the information displayed in the All Changes table.

...

The Run Statistics History view displays Oracle run statistics from when the statement has been run manually from within the tool. Any changes that it makes are rolled back. The only overhead is the execution time. A time-out may be specified in the Run dialog box to prevent the statement from taking too long. See “Running a statement” on page 155 Running a statement.

The Run Statistics History is a useful way of testing the performance of different SQL alternatives to see which is the fastest before it is put into production. Until it is run, the Collector will not have captured its execution performance. Another use is to benchmark the performance of certain key statements over time.

...

1. Identify the finding with the highest severity rank in the Findings table.
2. Select the finding type to view the expanded information for this type of operation.
3. Read the Highlights and What To Do Next areas for the finding and perform the advice that best suits your needs.
4. Follow up on performance to verify that the problem was resolved.

Anchor
Aboutastatementsdifferentversions Aboutastatementsdifferentversions

About a statement's different versions

The Compare view lists the different versions of a statement that have been saved together. It lets you compare Oracle Optimizer cost and execution statistics for each alternative so that you can choose the most efficient one. You can create related statements by doing any of the following:

...

1. Click Actions>Edit Text. The Edit Statement dialog box opens.
2. In the Edit Statement dialog box, do one of the following:
   • Enter a new name for the statement in the text field to rename the existing statement.
   • Enter a new name for the statement, check the Save as alternative option to save your changes under a different name.
   Either choose or save it as a related statement by entering a new name. If the statement was collected by the Collector, you can only save it under a new name. In this case, the Save as alternative option is pre-selected and cannot be unchecked. See “About About a statement's different versions” on page 151versions.
3. In the Text box, edit the SQL text for the statement.
4. Click Save. The edited statement is saved in the same cabinet and folder as the original.

Anchor
Runningastatement Runningastatement

Running a statement

The Run option lets you run a statement in the monitored database so that you can gather its execution statistics. Any changes that it makes are rolled back. The only overhead is the execution time. A timeout may be specified in the Run dialog box to prevent the statement execution from running too long.

...

1. Click Actions>Run.
2. On the General tab in the Run Statement dialog box, do the following:
   1. Select the database instance that the statement will run on. The maximum number of items displayed in the Cabinet, Folder, and Statement lists is limited.
   2. In the Description box, type a short description of the run.
   3. Enter the Oracle user name and password with which to log in to Oracle.
   4. Choose one of the following options: Fetch all rows or Fetch first n rows
   5. Specify the number of times that you want to run the statement. You may want to run it more than once to reduce the effect of having to load the buffer cache on the first run. Precise for Oracle calculates and displays the average value for each statistic over the series.
   6. Check the Time out after n minutes or hours, if you want to configure a timeout after which the execution of the statement is aborted if the timeout is exceeded. If this is an alternative version of a statement that you have saved, a reasonable timeout is the duration of the original version because you are unlikely to be interested in slower alternatives.
   7. Check Run in background, if you want to run the statement in the background.
3. On the Bind variables tab in the Run Statement dialog box, choose the bind variables with which to run the bind set as follows:
   1. Click Choose bind set.
   2. In the Bind Sets dialog box, choose the bind set you want to use to run the statement. see “About bind sets” on page 156 About bind sets.
   3. Click OK.
4. On the Advanced tab in the Run Statement dialog box, specify the session parameters to be used when running the statement:
   1. Type in a value for each session variable that you want to run the statement with.
   2. Click Add New Row if you want to add a new session parameter. Choose a session parameter name from the list, or enter a new one. Type in the value you want to run the statement with. See “About session parameters” on page 156 About session parameters.
   3. If you want to delete a session variable from the statement run, select the session variable you want to delete and click Delete.
   4. Click OK.
   5. Check the Extended run information (STATIC_LEVEL=ALL) option if you want additional statistics to be collected. These statistics are displayed in the Extended Statistics tab in the Run Alternatives view.
   6. Check the Array fetch option and specify the number of rows you want to be fetched, if you want to use an array fetch operation.
5. Click Fill Binds.
6. Click OK.

Anchor
Aboutbindsets Aboutbindsets

About bind sets

Bind variables are placeholders in a statement. When you use bind variables, you increase the probability that statements will be stored in memory, making them more immediately available to the next operation that needs them. Bind variables obtain their values from the last statement that was run. You can change the values of bind sets and analyze the values used when a statement is run, to help improve your tuning process.

Anchor
Aboutsessionparameters Aboutsessionparameters

About session parameters

Session variables obtain their values from the last statement run. You can define a new session variable to run the statement with, in the Add Session Parameters dialog box.

...

You can set the parsing user from Settings>General Settings>SQL tab. You can re-explain a statement in the following views:

• Plan
• All Plans

See “About About configuring your settings” on page 26 and settings and Editing the properties of a statement.

...

You can generate new statement alternatives in the Run Alternatives view. see “About See About configuring your settings” on page 26settings.

To generate a new alternative, in the Run Alternatives view, click Actions>Generate Alternative.

...