Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Overall Activity view, in the Activity tab, displays a stacked bar graph on the Overall Activity resource consumption over time, for the selected time frame, broken down into the Overall Activity wait states. See Overall activity.

Anchor
AbouttheImportedStatemententity
AbouttheImportedStatemententity
About the Imported Statement entity

Statements can be imported from external source files into Precise for Oracle and stored in the cabinet and folder hierarchy. To display them in the Activity tab, use the More... option in the Association area and click Imported Statements.

...

The Activity tab offers a unique method for identifying I/O problems in EMC and HP storage devices. It reports I/O wait time instead of just I/O counters. This lets you easily identify the resource that is actually being waited for and tune it instead of guessing by rules of thumb. Furthermore, you can associate the storage device with the applications and statements that are waiting on I/O.

See “Precise Precise for Storage, Oracle version - how resource consumption of storage devices is examined” on page 41examined.

Info

To look at a storage device in detail or to understand its performance over time, you can launch the Object tab by clicking the Object tab button for a storage device in the Main area or the launch icon for a storage device in the Association area.

...

The Import Statement button opens the Import Statements from File dialog box, allowing you to import SQL statements from a file. This dialog box includes three tabs: Source, Catalog, and Options. See Editing the properties of a statement and “About and About the Imported Statement entity” on page 78entity.

Defining information on the Source tab

...

Having identified a major resource consuming entity, you can further drill down to the statements and PL/SQL executed by that entity. These may include long running SQL statements and SQL statements that use few resources but were executed frequently. See “Identifying Identifying heavy resource consumers” on page 83consumers.

In many cases, analyzing the queries executed by the entity and tuning them will result in the most performance gain. For each statement, you can do the following:

...