Page History
This section includes the following topics:
- About the Oracle Activity by Instance portlet
- About the Oracle Activity Over Time portlet
- About the Oracle Business View portlet
- About the Oracle Top Programs portlet
- About the Oracle Top Statements portlet
- About the Oracle Top Users portlet
- About the SQL Server Activity by Database portlet
- About the SQL Server Activity Over Time portlet
- About the SQL Server Business View portlet
- About the SQL Server Top Programs portlet
- About the SQL Server Top Statements portlet
- About the Sybase Activity by Database portlet
- About the Sybase Business View portlet
- About the Sybase Top Statements portlet
| Anchor | ||||
|---|---|---|---|---|
|
The Oracle Activity by Instance portlet displays the Oracle activity by instance in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-1 Oracle Activity by Instance fields
| Field | Description |
|---|---|
| Instance | Displays the Oracle database instances included in the same application. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database, using the database link. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database, using the database link. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of Oracle programs with SLA settings that did not meet Oracle programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Oracle programs with SLA settings that are close to their Oracle programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Oracle programs with SLA settings that did meet the Oracle programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
The Oracle Activity Over Time portlet displays the overtime resource usage of the selected instance.
To view data in this portlet, verify that Precise for Oracle is installed in the selected application, and that it is integrated with Insight.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-2 Oracle Activity Over Time fields
| Field | Description |
|---|---|
| Date and Time | Displays the date and timestamp of the data available in the selected time frame. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database, using the database link. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database, using the database link. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of Oracle programs with SLA settings that did not meet Oracle programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Oracle programs with SLA settings that are close to their Oracle programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Oracle programs with SLA settings that did meet the Oracle programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
For information regarding the Oracle Business View portlet, see About the Oracle Business View portlet.
| Anchor | ||||
|---|---|---|---|---|
|
The Oracle Top Programs portlet displays the top Oracle programs in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify that Precise for Oracle is installed in the selected application, and that it is integrated with Insight.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-3 Oracle Top Programs fields
| Field | Description |
|---|---|
| Program | Displays the top Oracle program or programs. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database, using the database link. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database, using the database link. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of Oracle programs with SLA settings that did not meet Oracle programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Oracle programs with SLA settings that are close to their Oracle programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Oracle programs with SLA settings that did meet the Oracle programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
The Oracle Top Statements portlet displays the top Oracle statements in a selected instance or in all instances in the selected Tier. This view easily identifies the statements consuming the most resources.
To view data in this portlet, verify that Precise for Oracle is installed in the selected application, and that it is integrated with PMDB and Insight.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-4 Oracle Top Statements fields
| Field | Description |
|---|---|
| Statement | Displays the hash values of the top SQL statements running in an Oracle database. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database, using the database link. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database, using the database link. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of Oracle programs with SLA settings that did not meet Oracle programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Oracle programs with SLA settings that are close to their Oracle programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Oracle programs with SLA settings that did meet the Oracle programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
The Oracle Top Users portlet displays the top Oracle users in a selected instance or in all instances in the selected Tier. This view easily identifies the users consuming the most resources.
To view data in this portlet, verify Precise for Oracle is installed in the selected application, and that it is integrated with PMDB and Insight.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-5 Oracle Top Users fields
| Field | Description |
|---|---|
| User | Displays the top Oracle users in the selected application. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database, using the database link. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database, using the database link. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of Oracle programs with SLA settings that did not meet Oracle programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Oracle programs with SLA settings that are close to their Oracle programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Oracle programs with SLA settings that did meet the Oracle programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
The SQL Server Activity by Database portlet displays the SQL server activity by database in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-6 SQL Server Activity by Database field
| Field | Description |
|---|---|
| Database | The names of the SQL Server databases within SQL-Server instances. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of SQL Server programs with SLA settings that did not meet SQL Server programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of SQL Server programs with SLA settings that are close to their SQL Server programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of SQL Server programs with SLA settings that did meet the SQL Server programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
The SQL Server Activity Over Time portlet shows the use of the SQL Server activities belonging to the Tier and application that you selected, sorted by the fields that you selected, over a specified time period.
To view data in this portlet, verify that Precise for SQL Server is installed in the selected application, and that it is integrated with Insight.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-7 SQL Server Activity Over Time fields
| Field | Description |
|---|---|
| Date and Time | Displays the date and timestamp of the data available in the selected time frame. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of SQL Server programs with SLA settings that did not meet SQL Server programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of SQL Server programs with SLA settings that are close to their SLAs SQL Server programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of SQL Server programs with SLA settings that did meet the SQL Server programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
For information regarding the SQL Server Business View portlet, see About the SQL Server Business View portlet.
| Anchor | ||||
|---|---|---|---|---|
|
The SQL Server Top Programs portlet displays the top SQL server programs in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify that Precise for SQL Server is installed in the selected application, and that it is integrated with Insight.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-8 SQL Server Top Programs fields
| Field | Description |
|---|---|
| Program | Displays the top SQL Server program or programs. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of SQL Server programs with SLA settings that did not meet SQL Server programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of SQL Server programs with SLA settings that are close to their SQL Server programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of SQL Server programs with SLA settings, that did meet the SQL Server programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
The SQL Server Top Statements portlet displays the top SQL server statements in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify that Precise for SQL Server is installed in the selected application, and that it is integrated with PMDB and Insight.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-9 SQL Server Top Statements fields
| Field | Description |
|---|---|
| Statement | The hash values of top SQL statements running in the SQL server instance. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of SQL Server programs with SLA settings that did not meet SQL Server programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of SQL Server programs with SLA settings that are close to their SQL Server programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of SQL Server programs with SLA settings that did meet the SQL Server programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
The Sybase Activity by Database portlet displays the Sybase activity by database in a selected instance or in all instances in the selected Tier. This view easily identifies the databases consuming the most resources.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-10 Sybase Activity by Database fields
| Field | Description |
|---|---|
| Database | The names of the Sybase databases within Sybase instances. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of SQL Server programs with SLA settings that did not meet SQL Server programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of SQL Server programs with SLA settings that are close to their SQL Server programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of SQL Server programs with SLA settings that did meet the SQL Server programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
| Anchor | ||||
|---|---|---|---|---|
|
For information regarding the Sybase Business View portlet, see About the Sybase Business View portlet.
| Anchor | ||||
|---|---|---|---|---|
|
The Sybase Top Statements portlet displays the top Sybase statements in a selected instance or in all instances in the selected Tier. This view easily identifies the statements consuming the most resources.
To view data in this portlet, verify that Precise for Sybase is installed in the selected application, and that it is integrated with PMDB and Insight.
| Info |
|---|
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes. Poor service is the sum of the SLA Breach and SLA Near-Breach counters. |
The following table describes the fields displayed in this portlet.
Table 9-11 Sybase Top Statements fields
| Field | Description |
|---|---|
| Statement | The hash values of top statements running in the Sybase instance. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local database. |
| Remote DB Times (Summed) | Displays the time the SQL statement waited for a response from the remote database. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time spent in the local database. |
| Remote DB Time (Avg) | Displays the average time the SQL statement waited for a response from the remote database. |
| Executions | Displays the number of times an SQL statement was executed. |
| SLA Breach | Displays the percentage of SQL Server programs with SLA settings that did not meet SQL Server programs' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of SQL Server programs with SLA settings that are close to their SQL Server programs' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of SQL Server programs with SLA settings that did meet the SQL Server programs' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.