Skip to Content

Starting all concurrent managers

Use the following procedure to start up all concurrent managers by starting the Internal Manager. Since the Internal Manager controls all concurrent managers, starting the Internal Manager will subsequently start all concurrent managers.

Before you begin

  • Make sure you have access to the OS applmgr user name and password.
  • Identify the requests that are currently running by reviewing the ListRunningPendingReq parameter (for requests in Normal status) and the ListRunningPendingPausedReq parameter (for requests in Paused, Waiting, or No Manager status), which are located within CONC_REQUEST (OA_REQUEST application).

To start all concurrent managers

  1. Follow the applicationID (OA_SYSTEM) > CONC_MGR (OA_CONM) pathway.
    The INTERNAL_MGR (INT_MGR) icon appears.
  2. From the INTERNAL_MGR menu, select Startup Managers. The OS Account Info dialog box appears. There might be a delay as the Internal Manager on the host is contacted.
  3. Enter the operating system applmgr user name and password.
  4. In a multi-node environment, fill in the additional information:
    In the DB Apps Account fields, enter the Oracle user name and password.
    In the OA Environment File field, enter the location of the Oracle environment file.
  5. Click Accept. The Startup Managers dialog box reports the result of the command.
  6. If the Startup Managers command has not successfully completed after 3 minutes, the report process will stop, but the internal manager can be started successfully after 3 minutes.

If an error occurs

If the Internal Manager shuts down, a recovery dialog box notifies you of the manager's state and asks if you want to restart the internal manager. If you are running multiple console connections, the recovery action does not work because BMC PATROL for Oracle e-Business Suite is not able to distinguish which user response is the correct response to accept. In this case, the recovery dialog box provides instructions to manually start the Internal Manager.

The Shutdown Managers command does not abort any running requests. If a request is running, the shutdown process waits for the request to finish. If the managers have not shut down in 5 minutes, the shutdown process times out. You can run the Shutdown Managers command after the request has finished or kill the running requests.

Related topics

Selecting-concurrent-managers-for-monitoring
Deactivating-individual-concurrent-managers
Activating-individual-concurrent-managers
Shutting-down-all-concurrent-managers
Verifying-activity-of-all-concurrent-managers

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Oracle e-Business Suite 3.4