Page History
...
This section describes the available Oracle Applications parameters and how to use the tab. It does not, however, define the meaning of each Oracle Applications parameter or how to tune them; for this kind of information, see the appropriate Oracle documentation.Note:
| Info |
|---|
The Oracle Applications tab is only available if Interpoint for Oracle Applications has been installed. This is an optional extension to Precise for Oracle. For more information, see the Precise Installation Guide. |
See “Components of Precise for Oracle” on page 17, “About the Dashboard tab” on page 43, “About the Current tab” on page 51, and “About the Activity tab” on page 61.
...
When the Requests tab is selected, additional Action controls are displayed: a Concurrent Manager selector and a Request type selector. The Concurrent Manager selector lets you choose a specific Concurrent Manager or All Managers. The currently selected Concurrent Manager is retained when you move between the Manager view and the Requests view. If, for example, you select the Standard Manager in the Manager view and then click Requests, it will only display Requests submitted to the Standard Manager.
...
The Oracle Applications tab displays information on Concurrent Managers and Requests.
Viewing information about Concurrent Managers
On the Mangers tab, the Main area displays a table that provides information on all Concurrent Managers. The following table describes the information displayed.
Table 11-1 Concurrent Manager information in the Main area
Column Description
...
| Column | Description |
|---|---|
 | Indicates when the state of the Concurrent Manager is Stale. This column is empty for all other states. |
| Status |
...
State of the Concurrent Manager, which can be Active, Running, Terminated, Inactive, or Stale. |
| Concurrent |
...
| Manager | Name of the Concurrent Manager. |
| Pending |
...
| Requests | Number of pending requests that are queued. |
| Running |
...
| Requests | Number of requests that are currently running. |
| Running |
...
| Processes | Number of Concurrent Manager processes that have been started. |
| Available |
...
| Processes | Number of Concurrent Manager processes that have not been started. |
The Details area shows specifics on the Concurrent Manager that is selected in the Main area. The information in this area is displayed on the Overview and the Processes tabs.
About the overview of Concurrent Managers
The Overview tab identifies the Concurrent Manager and gives general information about it. It also shows a graph of the number of pending and running requests over time. A request normally starts as Pending and changes later to Running, so it should contribute to both totals. If there is a backlog, the pending total will be greater than the running total for each time interval.
About Concurrent Manager processes
The Processes tab displays a table that provides details on the different processes. The following table describes the information displayed.
Table 11-2 Concurrent Manager table on the Processes tab
| Column |
|---|
...
| Description |
|---|
...
|
...
Indicates when the state of the process is Fault. This column is empty for all other states. | |
| Process ID | Process |
...
| ID of the Concurrent Manager process. |
| Start |
...
| At | Date the process was started. |
| Oracle Process ID | Process |
...
| ID of the Oracle server process. If the Concurrent Manager process is not connected and there is a fault, this column may provide extra information. |
In addition, this tab displays a History graph that illustrates the availability of the Concurrent Manager processes over time, as follows:
- Processes Target—the Target. The total number of Concurrent Manager processes on a particular day.
- Processes Target OK and Processes Target Missed—represent Missed. Represent the average number of running processes on that day and whether the target was hit or not.
Viewing information about Requests
On the Requests tab, the information in the Main area is displayed on the Requests and the Arguments tabs. Both show a list of Requests filtered by the currently selected Oracle Applications instance, Concurrent Manager, and Request type. The difference lies in the columns that are displayed on each tab. The Requests tab provides the execution context; the Arguments tab shows the program that is executed, and its related arguments.
...
Table 11-3 Request information in the Main area
Column Description
ID Request ID
...
| Column | Description |
|---|---|
| ID | Request ID. |
| Program | Oracle Applications program that this Request executes. |
...
| Manager | Requests tab only. Concurrent Manager handling this Request. |
...
| User | Requests tab only. Oracle Applications user name. |
...
| Phase | Requests tab only. Execution phase of the Request. The Request can be Inactive, Scheduled, Pending, Running, or Completed. |
...
| Status | Requests tab only. Completion or success status of the Request. The Request can be Normal, Warning, Error, or Cancelled. |
| Elapsed |
...
| Time | Requests tab only. Time the request has spent in the Pending and Running states. |
| Argument 1 to |
...
| 5 | Argument to the Oracle Applications program. |
The Details area shows specifics on the Request that is selected in the Main area. The information is this area is displayed on the following tabs:
- Overview—shows Overview. Shows the status of the Request, its identification details, and its executed program details.
- Last 14 Day History—displays History. Displays the following pie charts:
- Total Time (Same program, various arguments)
...
- . Proportion of time that all Requests with the same program name as this Request have spent either pending or running during the last 14 days.
- Total Time (Same program, same arguments)
...
- . Proportion of time that all Requests with the same program name and arguments as this Request have spent either pending or running during the last 14 days.
- Completions (Same program, various arguments)
...
- . Proportion of successful and unsuccessful executions of all programs with the same name as this Request during the last 14 days. It also displays general information about the executed program.
- Completions (Same program, same arguments)
...
- . Proportion of successful and unsuccessful executions of all programs with the same name and arguments as this Request during the last 14 days. It also displays general information about the executed program.
- Details—more Details. More specifics on the request, such as whether it has a sub-request, its completion code, its schedule, and its output destination.
...
- On the Precise toolbar, click Settings>General Settings.
- Specify for how many days you want to view the Concurrent Manager history.
- Specify for how many hours you want to view the Concurrent Manager request history.
- Click OK.
| Anchor | ||||
|---|---|---|---|---|
|
You can identify a performance problem by doing one or more of the following:
| Anchor | ||||
|---|---|---|---|---|
|
The Concurrent Manager backlog shows us the number of requests (submitted to the Standard Manager) during a period of time. For our example, the Oracle Applications tab shows us that on Sept. 15, 33 requests were submitted to the Standard Manager in the first hour of September 15 and were therefore pending. Also 33 requests were run. In this case, even at the peak workload around midnight each day, it would appear that the Standard Manager processes were able to keep up with the workload. They at least ran the requests within an hour of being submitted.
...
- In the Time Frame list, choose the period of time you want to analyze.
- Open the Oracle Applications tab to view the number of submitted requests.
| Anchor | ||||
|---|---|---|---|---|
|
Ideally, all Concurrent Manager processes should be available to do work. To determine Concurrent Manager availability
- In the Time Frame list, choose the period of time you want to analyze.
- Open the Oracle Applications tab to view the number of available processes.
- Click the Processes tab. Examining the Processes tab, for the Standard Manager, shows that the number of available processes has not always hit the target figure. On September 15, the average number of processes available was 7.21 out of 16. Looking at the current state of the processes identifies that they cannot connect to Oracle, perhaps because it is unavailable.
| Anchor | ||||
|---|---|---|---|---|
|
The Oracle Applications tab shows the performance of related requests. To examine requests
- In the Time Frame list, choose the period of time you want to analyze.
- Open the Oracle Applications tab to view the number of submitted requests.
In the Main area, for our example, we see that Request 2160224 completed normally. The Details area displays the past performance of related requests.
The top two pie charts reveal that related requests spent approximately twice as long executing as they did waiting to be executed, regardless of which arguments were passed. The bottom two pie charts show the proportion of successful to unsuccessful executions.
The program has exited with an error code on 3 occasions, but has always been successful when executed with exactly the same arguments as the selected request. In other words, it has only failed when passing different arguments to the current request.
Precise. Performance intelligence from click to storage. Learn more > >
...