Viewing Top PeopleCode SQL Statements
Access the Top PeopleCode SQL page (PeopleTools, Performance Monitor, Analytics, Top PeopleCode SQL).
The data for this page is generated from the sum of all PMU 406 (PeopleCode SQL Execute) rows, and the data relates to the SQL that PeopleCode programs run.
The bars on the chart are links that you can click to access the Completed PMU history component. The system automatically populates the search criteria with values derived from the Top PeopleCode SQL Statements page. For example, PMU Identifier is set to406, and theContext 2 andStatement Number values are set appropriately.
All charts have a View in Grid hyperlink to show the chart information in a grid. This also enables you to sort the information and to download to Microsoft Excel spreadsheets.
|
Field or Control |
Definition |
|---|---|
| System ID |
Identifies each monitored system. PeopleSoft automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system. |
| Database Name |
The name of the PeopleSoft application database running on the monitored system. The monitoring system automatically inserts this value when it recognizes and creates a monitored system. |
| User ID |
The user ID of the user who generated the request. The User ID field prompts against the PSPMOPRDEFN table, which is populated by the Lookup program (PSPM_LOOKUP). |
| Performance Trace Name |
You enter the performance trace name to search on PMUs within a particular performance trace. If a user has launched a performance trace in the Performance Console, the system labels every PMU that is generated in a business process with a performance trace name. Performance Trace Name prompts against the PSPMPERFTRACE table, which is populated by the Lookup program (PSPM_LOOKUP). Note: When searching using a performance trace name, the search ignores all agent IDs, so the current system ID is not relevant. |
| Component |
Select the component name. |
| Market |
Select the market to which the component belongs. |
| From/To Date/Time |
Specify a range of time. The system searches on the monitor date and time, not the agent date and time. If you do not specify a time range, by default, the system displays information for the current day, starting at midnight (12:00 AM). |
| Search |
The Search button performs a search based on the search criteria that is defined on the page. It should be pressed only once per search. If you want to view the most current information, use theRefresh button after running the initial search. If you clickSearch repeatedly, the system returns the same results from the same time range for each search. |
| Number to Retrieve |
The number of top ranked statistics to be displayed on the charts. |
| Refresh |
Updates the To Time value to equal the current time. Enables you to view the most current results of a search. |
Top SQL Statements
This chart indicates the PeopleCode SQL statements that the system runs the most.
SQL statements are identified by PeopleCode locations, such as PeopleCode Program and PeopleCode Statement Number (context 2 and metric 2).
Top Cumulative Durations
Identifies the PeopleCode SQL statements with the longest cumulative durations.
SQL statements are identified by PeopleCode locations, such as PeopleCode Program and PeopleCode Statement Number (context 2 and metric 2).
Duration Averages
Identifies the PeopleCode SQL statements with the longest average durations.
SQL statements are identified by PeopleCode locations, such as PeopleCode Program and PeopleCode Statement Number (context 2 and metric 2).
Note: This data is available only when the agent filters on the application server are set to verbose or debug, or performance traces were run with a filter level set to debug or verbose. A small, yellow triangle appears at the top of the page alerting you if application servers for that system are currently at a higher filter level than verbose. This, however, does not mean that you would not see data; PMUs may exist from performance traces or lower filter levels from past monitoring.