Page History
...
| Info |
|---|
If you are working with Oracle Applications, SAP, PeopleSoft, or Siebel and ERP support is installed, the Activity tab displays information on the historical Oracle activity in relation to the ERP application and users, and specific information on executed forms (Oracle Applications) and transactions (SAP). |
See “Precise Precise Interpoint - how resource consumption of packaged applications is examined” on page 40examined.
| Anchor | ||||
|---|---|---|---|---|
|
...
You can use the Filter dialog box to filter the Association area so that only the contribution of certain entities is included. See “Filtering data” on page 29 Filtering data.
About the Table view
The Table view is divided into two areas, the Main area and the Association area. Information on the entity you are analyzing is displayed in the Main area. The entities that are associated with the entity displayed in the Main area are displayed in Association area.
...
The duration value displayed next to each entry reflects the duration of each instance in the selected entity, according to the sort parameter you selected. The sort parameter is displayed next to each entity. The default entity for the top entity in the tree is In Oracle time. You change this setting in the Settings dialog box. See “About About configuring Tree view settings” on page 27settings.
| Info |
|---|
The following entities are not displayed in the Tree view: Recent Sessions, Extended Collections and Imported Statements. The Database entity is only displayed when All Instances is selected. |
...
You can switch to a different time frame and view additional information on the selected entity that was collected for that time frame. Only the information in the subnodes sub-nodes of the entity you have selected is refreshed.
...
The Refresh option refreshes the display from the PMDB.
To refresh the information displayed in a view
...
You can print an image of what is displayed in the Tree view.
To print the Tree View display
...
The Overview displays general information about the selected entity and a table listing the In Oracle sub-states for this entity. See “In Oracle” on page 36 Wait States - In Oracle.
The following table describes what is displayed in the overview.
...
The In Oracle view displays a stacked bar graph on the In Oracle resource consumption over time, for the selected time frame, broken down into the In Oracle wait states. See “In Oracle” on page 36 Wait States - In Oracle.
About the overall activity view
The Overall Activity view 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” on page 35 Overall activity.
About the scalability view
...
| Graph | Description |
|---|---|
| Availability | Compares 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 Times | Indicates the amount of time that the instance or instances were unavailable. |
...
The Statistics view displays a table that indicates a change in Oracle statistics for the selected entity during the specified time frame. The Statistics column displays statistics that represent different counters with different units. For more information, see the Oracle documentation . See “Oracle and Oracle statistics usage within Precise for Oracle” on page 40Oracle.
About the RAC database view
...
| Item | Description |
|---|---|
| Database | Displays the logical name of the RAC database. |
| DB Name | Displays the Oracle database ID for the instance. |
| DB ID | Displays the Oracle database ID. |
| In Oracle (Sum.) | Total time the instance spent In Oracle. |
| Sessions | Total 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 Counts | Number of executions. |
| In Oracle (Avg.) | Average In Oracle time for all instances in the RAC database. |
| Instances | Displays 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 table | Shows 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. |
...
You can also save a statement. See “Editing Editing the properties of a statement” on page 31statement.
The following views are available for a statement and PL/SQL entity:
...
If bind variables were captured for a statement, a link is displayed that launches to the Bind Variables tab in the SQL tab, with the statement in context, to run a statement with the actual bind variables that are being used. If you drill down to a statement from an execution plan entity, and execution plans were captured for the statement, a link is displayed that launches to the All Plans tab in the SQL tab, with the statement in context. See “In Oracle” on page 36 and “About Wait States - In Oracle and About the Bind Variables view” on page 148view.
The following table explains how the general information is structured.
...
| Item | Description |
|---|---|
| In Oracle (Sum.) | Total time the statement or PL/SQL spent In Oracle. |
| Executions/Execution Counts | Number of times the statement or PL/SQL was executed. See “Executions Executions vs. opens and fetches” on page 39fetches. |
| 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 Count | Number of times the statement returned all rows to the user rather than returning only the first rows and dropping the cursor. “End End of fetch count” 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 In Oracle view displays a stacked bar graph in the Activity tab on the In Oracle resource consumption over time, for the selected time frame, broken down into the In Oracle wait states. See “In Oracle” on page 36 Wait States - In Oracle.
About the overall activity of a statement or PL/SQL
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 overall activity wait states. See “Overall activity” on page 35See Overall activity.
About the scalability of a statement or PL/SQL
...
The Statistics view, in the Activity tab, displays a table indicating a change in Oracle statistics for the selected statement or SQL during the specified time frame. The Statistics column displays statistics representing different counters with different units. For more information, see the Oracle documentation . See “Oracle and Oracle statistics usage within Precise for Oracle” on page 40Oracle.
About the text view of a statement or PL/SQL
...
| Item | Description |
|---|---|
| Parsing User | Oracle user name used to explain and parse the statement. |
| Cabinet | Name of the cabinet where the statement is stored. |
| Folder | Name 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:
|
| Comment | User-defined comment associated with the statement. |
See “Editing Editing the properties of a statement” on page 31. See “About the SQL tab” on page 131statement and About the SQL tab.
About the Execution Plan entity
...
The Overview, in the Activity tab, displays general information about the selected entity, a table that lists the In Oracle sub-states for this entity, and the complete SQL text of the SQL statement. See “In Oracle” on page 36 Wait States - In Oracle.
The following table describes the information displayed for an execution plan.
...
The In Oracle view, in the Activity tab, displays a stacked bar graph on the In Oracle resource consumption for the execution plan, over time, broken down into the In Oracle wait states. See “In Oracle” on page 36 Wait States - In Oracle.
About the overall activity view of an execution plan
The Overall Activity view, in the Activity tab, displays a stacked bar graph describing the overall activity resource consumption of the execution plan over time, broken down into overall activity wait states. See “Overall activity” on page 35See Overall activity.
About the scalability view of an execution plan
...
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. See “IWait States - I/O wait” on page 38wait.
About In Oracle data for an object
The In Oracle view, in the Activity tab, displays a stacked bar graph on the In Oracle resource consumption over time, for the selected time frame, broken down into the In Oracle wait states. Particularly important for an object is the amount of time spent in I/O wait, Internal Lock wait, and Application Lock wait, that is how well cached the object is. See “In Oracle” on page 36 Wait States - In Oracle.
About the dictionary view of an object
...
The Overview, in the Activity tab, displays a table listing the I/O Wait sub-states for this Oracle file. 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. See “ISee Wait States - I/O wait” on page 38wait.
About the In Oracle view of an Oracle file
...
The Dictionary view, in the Activity tab, describes the properties of the Oracle file. The information displayed is equivalent to information that can be found in the DBA_DATA_FILES table.
| Anchor | ||||
|---|---|---|---|---|
|
You can define an Extended Collection when you need to carry out a more intensive investigation into a particular performance problem. It lets you capture trace-level information from Oracle, allowing you to see Oracle wait event information for sessions and statements. You can, for example, find a unique index contention or ITL contentions.
...
- Overview
- In Oracle
- Overall Activity
See “Defining extended collections” on page 80 and “Filtering data” on page 29. Defining extended collections and Filtering data.
About the overview of an extended collection
The Overview, in the Activity tab, displays general information about the Extended Collection for the specified time frame and a table that lists the In Oracle sub-states for this entity. See “In Oracle” on page 36 Wait States - In Oracle.
The following table describes how the general information for an extended collection is structured.
...
| Item | Description |
|---|---|
| Status | Status of the collection, which can be one of the following: Pending, Completed, Running, or Stopped. |
| Criteria | List of programs and other criteria that are included or excluded in the collection. |
| Current Size | Size of the collection. The size is limited when the collection is created. See “Defining extended collections” on page 80 Defining extended collections. |
| Start Collecting at | Start date and time of the collection. |
| Stop Collecting at | End date and time of the collection. |
...
The In Oracle view, in the Activity tab, displays a stacked bar graph on the In Oracle resource consumption over time, for the selected time frame, broken down into the In Oracle wait states. See “In Oracle” on page 36 Wait States - In Oracle.
About the overall activity view of an extended collection
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” on page 35See Overall activity.
About Session and Recent Session entities (in Table view only)
...
In addition, Precise for Oracle keeps the last n hours of session information on the server and makes it available using Recent Sessions. By default, information for the last 4 four hours is saved. You can specify and change the length of time using Precise Agent Installer (see the Precise Installation Guide for detailssee Installation and Administration), but increasing it will obviously require more storage.
...
- Overview
- In Oracle
- Overall Activity
See “About About the Extended Collection entity” on page 75entity.
About the overview of a session or recent session
The Overview, in the Activity tab, displays general information about the Session (in an Extended Collection) or Recent Session for the specified time frame and a table listing the In Oracle sub-states for this entity (for details on these sub-states, see See “In Oracle” on page 36 Wait States - In Oracle.).
The following table describes how the general information for a session or recent session is structured.
...
The In Oracle view, in the Activity tab, displays a stacked bar graph on the In Oracle resource consumption over time, for the selected time frame, broken down into the In Oracle wait states. See “In Oracle” on page 36 Wait States - In Oracle.
About the overall activity of a session or recent session
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” on page 35.See Overall activity.
| Anchor | ||||
|---|---|---|---|---|
|
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 option in the Association area and click Imported Statements.
...
| Item | Description |
|---|---|
| Explained on | The date and time of the last explain. |
| Parsing User | Oracle user name used to explain and parse the statement. |
| Cabinet | Name of the cabinet where the statement is stored. |
| Folder | Name of the folder where the statement is stored. |
| Origin | Source of the statement. In this case, it is always Imported from source file. |
| Cost | The cost of the imported statement. |
| Saved on | Information on when the imported statement was saved. |
| Statement | The name of the imported statement. |
| Oracle Hash Value | The Oracle Hash value of the imported statement. |
| Comment | User-defined comment associated with the statement. This is blank until the statement has been saved. |
See “Editing Editing the properties of a statement” on page 31 and “About the SQL tab” on page 131.statement and About the SQL tab.
About storage device entities
...
| Info |
|---|
These entities are only available if you have installed Precise for Storage. For more information on the supported platforms, see the Precise Installation Guideand Administration. |
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 Overview, in the Activity tab, displays a table listing the In Oracle sub-states for this storage device. See “In Oracle” on page 36 Wait States - In Oracle.
The following table describes the In Oracle (Sum.) table for an extended collection.
...
See “Editing Editing the properties of a statement” on page 31statement.
| Anchor | ||||
|---|---|---|---|---|
|
...
Using the Define Extended Collection dialog box, you can specify the instance that you want to monitor, the name of your collection, the start and stop time, and the maximum size of the trace. You then use the entity table to define the entities that you want to include or exclude. In the Include and Exclude fields, you can use the Oracle SQL-style wildcards ‘'-’ ' and ‘%’ '%' to match zero or more characters and ‘'_’ ' to match a single character. The AND operator is used to produce the final selection.
| Info |
|---|
Try to only include the entities that you need and do not run too many extended collections simultaneously. Although the overhead is still much less than for SQL_TRACE, there can be a slight performance penalty in having to write a lot of information to the traces file on the monitored server. |
See “About About the Extended Collection entity.
entity” on page 75. To define extended collections
- Click the Define Extended Collection button to open the Define Extended Collection dialog box.
- In the Instance list, select the appropriate instance name.
- If appropriate, type in the Collection name.
- For Start At date and time, select the following data:
- day (number)
- month (name)
- year (number)
- hour (number)
- minute (number)
- Type the desired maximum number of megabytes for collection information.
- Define the criteria for activities to be gathered in the collection. For each entity listed in the Entity column, define whether to include or exclude the entity to the collection.
- Click OK to accept or Cancel to reject the defined entities.
...
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 Editing the properties of a statement” on page 31. See “About statement and About the Imported Statement entity” on page 78entity.
Defining information on the Source tab
...
If duplicates are detected during the import process, the newer version of a statement will not over-ride override the older version.
To define Source tab details
...
- In the Instance list, choose the item you want to analyze.
- In the Time Frame list, choose the period of time you want to analyze.
- On the View controls in the Main area, click Overview. Examine the entire instance and determine which are the dominant resources that are consumed by your system. For our example, we have an Activity tab that shows an instance that is fairly busy. In the Main area, the instance shows that it has spent 1 day out of 7 executing. But it has spent 40% of that time on Other Lock Wait. This is an unproductive wait.
Launch to the Statistics tab to find out more about the underlying Oracle wait events comprising the Other Lock Wait. It is most likely to be an enqueue. In fact, the instance has spent over 50% of its time in unproductive waits (not using CPU or I/O).
Info As a rule of thumb, a healthy system should have a high Using CPU value; a 10-15% I/O Wait, and the remaining non-productive wait states should show values that are as low as possible. For databases that process large data volumes, such as a data warehouse, the I/O Wait percentage may be higher. It is true, however, that applications/statements that experience high Using CPU or I/O Wait times may be performing excessive logical I/Os and should be investigated. To determine this, it is important to look at the actual time spent waiting (in hh:mm:ss) as well as just the percentage.
...
You can display the average duration for statements with the format shown as hh:mm:ss.
The following example shows how to drill down to application components and identify resource consumers. For our example, the Active tab shows a list of programs that you can drill down to in the Tree pane. We want to drill down to the program that spent the most time.
...
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:
...
Precise for Storage, Oracle version, supports EMC devices and lets you see the resource consumption of the EMC Storage devices from the application’s application's point of view.
The following example shows how to examine EMC Storage devices resource consumption. To examine EMC Storage devices
- In the Instance list, choose the item you want to analyze.
- In the Time Frame list, choose the period of time you want to analyze.
- 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.
- 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.
- Drill down into device 0E1 to see its resource consumption over time. Find out which statements have been waiting on it.