Versions Compared

Key

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

This section includes the following topics:

 

■    About the Oracle Applications tab 

■    How the Oracle Applications tab is structured 

■    About the information you can examine in the Oracle Applications tab 

■    Defining the settings of overtime graphs

 

■    How the Oracle Applications tab can help you identify performance problems 

 

About the Oracle Applications tab 

The Oracle Applications tab displays details about the current status of the Concurrent Managers and Requests (batch jobs and reports) that have been submitted. It also displays historical information on the availability of the managers and completion of requests. It has a structure similar to the Dashboard tab, allowing you to quickly monitor the health of your Oracle Applications instances.

...

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: 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. See the Precise Installation Guide.See , “About the Dashboard tab” on page 43. See , “About the Current tab” on page 51. See , and “About the Activity tab” on page 61. 

 

How the Oracle Applications tab is structured 

The Oracle Applications tab is divided into two views: Managers and Requests. Each view is also divided into two sections: the Main area on the left and the Details area on the right. Both areas can have additional tabs, depending on which view is selected.

...

The Request Type selector lets you choose All Requests, Current Requests, Past Requests and so on. By default, all Requests are shown.

 

 

About the information you can examine in the Oracle Applications tab 

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 1 Concurrent Manager information in the Main area

 

Column    Description 

    Indicates when the state of the Concurrent Manager is Stale. This column is empty for all other states.

...

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 2 Concurrent Manager table on the Processes tab

...

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 total number of Concurrent Manager processes on a particular day.

 

...

  • Processes Target OK and Processes Target Missed—represent the average number of running processes on that day and whether the target was hit or not.

 

Viewing information about Requests

...

The following table describes the information displayed. 

Table 11-3    Request 3 Request information in the Main area

...

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 the status of the Request, its identification details, and its executed program details.

 

...

  • Last 14 Day 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 specifics on the request, such as whether it has a sub-request, its completion code, its schedule, and its output destination.

...

 

...

Defining the settings of overtime graphs 

You can customize the time frame that is covered by the overtime graphs on the Managers and Requests tabs. See “About configuring your settings” on page 26.

To define the graph settings

 

...

  1. On the Precise toolbar, click Settings>General Settings.

 

...

  1. Specify for how many days you want to view the Concurrent Manager history.

 

...

  1. Specify for how many hours you want to view the Concurrent Manager request history.

 

...

  1. Click OK.

...

 

How the Oracle Applications tab can help you identify performance problems 

You can identify a performance problem by doing one or more of the following:

 

...

  • Examining Concurrent Manager backlog

 

...

  • Determining Concurrent Manager availability

 

■    Examining requests

 

...

  • Examining requests

Examining Concurrent Manager backlog

...

To examine the Concurrent Manager backlog

 

...

  1. In the Time Frame list, choose the period of time you want to analyze.

 

...

  1. Open the Oracle Applications tab to view the number of submitted requests.

...

 

...

Determining Concurrent Manager availability Ideally, all Concurrent Manager processes should be available to do work. To determine Concurrent Manager availability1    In

  1. In the Time Frame list, choose the period of time you want to analyze.

 

...

  1. Open the Oracle Applications tab to view the number of available processes.

 

 

...

  1. 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.

...

Examining requests

The Oracle Applications tab shows the performance of related requests. To examine requests1    In

  1. In the Time Frame list, choose the period of time you want to analyze.

 

...

  1. 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 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 > >

...