You can start, shut down, or reset the concurrent managers at any time. Oracle Applications provides an Internal Concurrent Manager that processes these commands. You can issue commands either to individual managers, or, by altering the state of the Internal Concurrent Manager, you can control every manager at once.
The Internal Concurrent Manager activates and deactivates individual managers and enforces run-alone program and program incompatibility rules. See: Controlling Managers.
You should restart an individual manager when you:
If you choose to Deactivate the manager, requests that are currently running are allowed to complete.
When you terminate requests and deactivate an individual manager, requests that are currently running are immediately stopped and marked for resubmission (when the manager is activated).
Oracle Applications concurrent programs are designed so that no data is lost or duplicated when a terminated request is resumed after a shut down. This applies for shutdowns that are normal (e.g., using the "Deactivate concurrent manager" request) or abnormal (e.g., after a hardware failure).
Attention: When a manager is selected and explicitly deactivated, it remains that way until you select and explicitly activate that manager. As a prerequisite, the Internal manager must be activated beforehand.
When you deactivate the Internal Concurrent Manager, it issues commands to deactivate all active managers. Managers that were deactivated on an individual basis are not affected.
If you terminate requests and deactivate the Internal Concurrent Manager, it issues commands to all other managers to terminate their requests and deactivate. Requests that are currently running are immediately stopped and marked for resubmission when the managers are activated.
You can instruct the Internal Concurrent Manager to immediately verify the operating status of your individual concurrent managers, or to perform a PMON check.
You can also have the Internal Concurrent Manager "manually" verify the status of your individual managers, and restart individual managers. See: Administer Concurrent Managers.
|Internal Manager||Activate concurrent manager||Activates the Internal manager and all other managers, except managers that were deactivated individually using "Deactivate concurrent manager".|
|Verify concurrent manager status||Manually executes the process monitoring (PMON) cycle.|
|Deactivate concurrent manager||Deactivates the Internal manager and all other managers.|
|Terminate requests and deactivate manager||All running requests (running concurrent programs) are terminated, and all managers are deactivated.|
|Any Other Manager||Activate concurrent manager||If the manager is defined to work in the current work shift, it starts immediately. Cancels "Deactivate concurrent manager" and "Terminate requests and deactivate manager".|
|Restart concurrent manager||Internal manager rereads the manager's definition, and the rules for concurrent program incompatibilities. You should restart a manager when you: - Change work shift assignments - Modify the number of target processes - Modify specialization rules - Change concurrent program incompatibilities|
|Deactivate concurrent manager||Deactivates the manager. All requests (concurrent programs) currently running are allowed to complete before the manager shuts down. A manager will not restart until you select the manager and choose "Activate concurrent manager".|
|Terminate requests and deactivate manager||All running requests (running concurrent programs) handled by the manager are terminated. Once deactivated, a manager will not restart until you select the manager and choose "Activate concurrent manager".|
|Table 1 - 19. (Page 2 of 2)|
Overview of Parallel Concurrent Processing
Administer Concurrent Managers field help