Monitoring concurrent managers

At the center of Oracle Applications is an executable called the concurrent manager. The concurrent manager controls the execution of concurrent requests. When a user requests a program to run, the request is inserted into a database table and identified by a request ID. The concurrent manager then reads the request from this table; if the concurrent manager is defined to accept and run this request, then it runs the request. This tool allows users to run requests; for instance, reports and batch programs in the background while they work in the application.

This section contains information about the following tasks:

A target process, or queue, is used to process requests. A concurrent manager can have several target processes. The number of target processes defines the number of operating system processes that a concurrent manager can devote to reading requests. The number of target processes is defined for a certain period of time — a work shift or other time definition. For each target process, a concurrent manager can start one concurrent request. By defining target processes on a time period basis, the concurrent manager utility becomes a scheduling tool. As a system administrator, you can schedule requests to run at a particular time or on a regular basis.

The Internal Manager (INTERNAL_MGR) controls all concurrent managers in your Oracle Applications environment. If you start the Internal Manager you will start all concurrent managers. Stopping the Internal Manager will stop all concurrent managers.

Related topics

Managing-bottlenecks
Monitoring-concurrent-requests
Alleviating long-pending and long-running requests
Monitoring-error-and-warning-requests
Monitoring-long-running-and-long-pending-requests
Managing concurrent manager bottlenecks
Setting-the-statistics-polling-interval