Versions Compared

Key

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

...

About the Tree view

Figure 5- 1 Oracle Activity tab Tree view

...

When selecting a category under the entity in the Tree view, the following details are available per category:

Table 5- 1 Details per category

CategoryDetails
Aggregated entitiesGeneral, In Oracle, Statistics
StatementsGeneral, In Oracle, Workshop
ObjectsGeneral, In Oracle, I/O Wait
Execution PlansGeneral, In Oracle
Oracle FilesGeneral, In Oracle, I/O Wait
PL/SQLsGeneral, In Oracle, Workshop

About aggregated entities in the Activity tab

...

The following table describes what is displayed in the overview.

Table 5- 2 General entity information

ItemDescription
Instance NumberDisplays the number of the instance in the RAC database.
In Oracle (Sum.)Total time the entity spent In Oracle.
SessionsTotal number of active sessions associated with the entity. An active session is one that executed or was executing a statement during the selected time frame and spent some time In Oracle.
In Oracle (Avg.)Total In Oracle time for the entity or number of active sessions associated with the entity.
Duration (Avg.)Average time active sessions associated with the entity were connected to Oracle.

The following table describes the In Oracle (Sum.) table.

Table 5- 3 In Oracle (Sum.) table

ColumnDescription
Sub-StateIn Oracle sub-state.
Bar graphGraphical representation of the Time column.
TimeAmount of time the entity was in this state.
%Percentage of time the entity was in this sub-state.

Additional information on In Oracle sub-states is available in the stacked bar graph of the In Oracle view and on the In Oracle tab of the table in the Association area.

...

The following table explains which graphs are shown for a specific entity.

Table 5- 4 Graphs displayed in the Scalability view

EntityGraphs
Instance

In Oracle (Avg.) vs. Sessions

In Oracle (Avg.) vs. Statement Executions

Program, User, Module, Action, Machine, Host UserIn Oracle (Avg.) vs. Statement Executions

About the availability view

...

The following table describes the stacked overtime graphs that are displayed in this view.

Table 5-5 Graphs displayed in the Availability view

GraphDescription
AvailabilityCompares the overall availability with the Availability SLA, in percent. The settings for the Availability SLA are defined in AdminPoint. For more information, see the Precise Administration Guide. Availability information is also displayed on the Overview tab in the Dashboard tab.
Unavailability TimesIndicates the amount of time that the instance or instances were unavailable.

About the statistics view

...

The RAC Database view compares activity of the selected instance to the activity of the all the instances in the entire RAC database. The RAC Database view is only available for RAC Database instances. The following table describes the information displayed in the RAC Database view.

Table 5- 6 RAC Database view

ItemDescription
DatabaseDisplays the logical name of the RAC database.
DB NameDisplays the Oracle database ID for the instance.
DB IDDisplays the Oracle database ID.
In Oracle (Sum.)Total time the instance spent In Oracle.
SessionsTotal number of active sessions associated with the instance. An active session is one that executed or was executing a statement during the selected time frame and spent some time In Oracle.
Executions CountsNumber of executions.
In Oracle (Avg.)Average In Oracle time for all instances in the RAC database.
InstancesDisplays the number of instances that share the same RAC database with the selected instance.
In Oracle (Avg. per instance)Average In Oracle time for the selected instance.
RAC Database tableShows additional details on the instances in the RAC database, such as the number of sessions run by each instance, the amount of time each spent actively executing statements and PL/SQLs within Oracle, and the number of statements executed by each instance.

About Statement and PL/SQL entities

...

The following table explains how the general information is structured.

Table 5- 7 Structure of general information for a statement or PL/SQL

ItemDescription
In Oracle (Sum.)Total time the statement or PL/SQL spent In Oracle.
Executions/Execution CountsNumber of times the statement or PL/SQL was executed. See “Executions vs. opens and fetches” on page 39.
In Oracle (Avg.)For a statement only. Total In Oracle time for the statement or number of executions. If Opens + Fetches are displayed, this field displays N/A.
Duration (Avg.)For a statement only. Total overall activity time for the statement or the number of executions.
Buffer Gets (Avg.)For a statement only. Total number of buffer gets for the statement or the number of executions. If Opens + Fetches are displayed, this field displays N/A.
Rows Processed (Avg.)For a statement only. Total number of rows processed by the statement or the number of executions. If Opens + Fetches are displayed, this field displays N/A.
Parallel Servers (Min.)Minimum number of parallel query slaves that executed the statement.
Parallel Servers (Max.)Maximum number of parallel query slaves that executed the statement.
End of Fetch CountNumber of times the statement returned all rows to the user rather than returning only the first rows and dropping the cursor. “End of fetch count” will always be less than or equal to executions.
Version Count (Max.)Shows the maximum number of cursors created for the particular statement in parallel.

The following table describes the In Oracle (Sum.) table for a statement or PL/SQL.

Table 5- 8 In Oracle (Sum.) table for a statement or PL/SQL

ColumnDescription
Sub-Statein Oracle sub-state.
Bar graphGraphical representation of the Time column.
TimeAmount of time the entity was in this state.
%Percentage of time the entity was in this sub-state.

Additional information on In Oracle sub-states is available in the stacked bar graph of the In Oracle view and on the In Oracle tab of the table in the Association area.

...

The following table describes how the information in the Workshop view is structured.

Table 5- 9 Structure of information in the Workshop view

ItemDescription
Parsing UserOracle user name used to explain and parse the statement.
CabinetName of the cabinet where the statement is stored.
FolderName of the folder where the statement is stored.
Origin

Source of the statement. The Collector captures most statements automatically when they execute. The following values are possible:

  • Unknown
  • Automatically collected
  • Generated as related SQL
  • Predicted plan (What-If)
  • Entered by user
  • Imported from source file
  • Generated as related SQL by user
CommentUser-defined comment associated with the statement.

See “Editing the properties of a statement” on page 31. See “About the SQL tab” on page 131.

...

The following table describes the information displayed for an execution plan.

Table 5- 10 General over of an execution plan

ItemDescription
In Oracle (Sum.)Total time spent in Oracle by statements using the selected plan.
Execution CountsNumber of executions performed by the statements.
In Oracle (Avg.)Displays the average time spent by the execution plan in the Oracle database.
Duration (Avg.)Displays the average activity time for the execution plan.
Buffer Gets (Avg.)Average number of buffer gets for the execution plan.
Rows Processed (Avg.)Average number of rows processed by the execution plan.

The following table describes the In Oracle (Sum.) table for an execution plan.

Table 5- 11 In Oracle (Sum.) for an execution plan

ColumnDescription
Sub-StateIn Oracle sub-state.
Bar graphGraphical representation of the Time column.
TimeAmount of time the entity was in this state.
%Percentage of time the entity was in this sub-state.

Additional information on In Oracle sub-states is available in the stacked bar graph of the In Oracle view and on the In Oracle tab of the table in the Association area.

...

The following table describes how the general information for an extended collection is structured.

Table 5- 12 Structure of general information for an extended collection

ItemDescription
StatusStatus of the collection, which can be one of the following: Pending, Completed, Running, or Stopped.
CriteriaList of programs and other criteria that are included or excluded in the collection.
Current SizeSize of the collection. The size is limited when the collection is created. See “Defining extended collections” on page 80.
Start Collecting atStart date and time of the collection.
Stop Collecting atEnd date and time of the collection.

The following table describes the In Oracle (Sum.) table for an extended collection.

Table 5- 13 In Oracle (Sum.) table for an extended collection

ColumnDescription
Sub-StateIn Oracle sub-state.
Bar graphGraphical representation of the Time column.
TimeAmount of time the entity was in this state.
%Percentage of time the entity was in this sub-state.

Additional information on In Oracle sub-states is available in the stacked bar graph of the In Oracle view and on the In Oracle tab of the table in the Association area.

...

The following table describes how the general information for a session or recent session is structured.

Table 5- 14 Structure of general information for a session or recent session

ItemDescription
In OracleTotal time the session spent in Oracle
UserOracle user name
Host UserHost user name.
MachineName of the machine connected to Oracle
Oracle Process IDOS-assigned process ID of the Oracle server process
Client Process IDProcess ID of the client or application process, if it is running on the same server as the instance; otherwise it is zero.
Oracle Process TypeType of Oracle server process: Dedicated, MTS, or Parallel.

The following table describes the In Oracle (Sum.) table for an extended collection.

Table 5- 15 In Oracle (Sum.) table for a session or recent session

ColumnDescription
Sub-StateIn Oracle sub-state.
Bar graphGraphical representation of the Time column.
TimeAmount of time the entity was in this state.
%Percentage of time the entity was in this sub-state.

Additional information on In Oracle sub-states is available in the stacked bar graph of the In Oracle view and on the In Oracle tab of the table in the Association area.

...

The following table describes how the information in the Workshop view is structured.

Table 5- 16 Structure of information

ItemDescription
Explained onThe date and time of the last explain.
Parsing UserOracle user name used to explain and parse the statement.
CabinetName of the cabinet where the statement is stored.
FolderName of the folder where the statement is stored.
OriginSource of the statement. In this case, it is always Imported from source file.
CostThe cost of the imported statement.
Saved onInformation on when the imported statement was saved.
StatementThe name of the imported statement.
Oracle Hash ValueThe Oracle Hash value of the imported statement.
CommentUser-defined comment associated with the statement. This is blank until the statement has been saved.

See “Editing the properties of a statement” on page 31 and “About the SQL tab” on page 131.

...

The following table describes the In Oracle (Sum.) table for an extended collection.

Table 5- 17 In Oracle (Sum.) table for a storage device

ColumnDescription
Sub-StateIn Oracle sub-state.
Bar graphGraphical representation of the Time column.
TimeAmount of time the entity was in this state.
%Percentage of time the entity was in this sub-state.

Additional information on In Oracle sub-states is available in the stacked bar graph of the In Oracle view and on the In Oracle tab of the table in the Association area.

...

  1. In the Instance list, choose the item you want to analyze.
  2. In the Time Frame list, choose the period of time you want to analyze.
  3. For our example, the Association area in the Activity tab shows the total I/O wait on each of the devices used by instance ora920 in just over one hour, broken down into scattered and sequential I/O types.
  4. Check the I/O wait on the devices. The I/O wait on devices, for our example, 0E1 and 0E0 is significantly higher than for 0DE and 0DF. These are the busy devices as far as this instance is concerned.
  5. Drill down into device 0E1 to see its resource consumption over time. Find out which statements have been waiting on it.

 

Precise. Performance intelligence from click to storage. Learn more > >

...