Setting thresholds for concurrent requests


Before you can use BMC PATROL for Oracle e-Business Suite to alert you to concurrent requests that are not performing, you must set the thresholds for long-running requests, and long-pending requests.

You can use the following procedures to customize the thresholds of concurrent processes:

To set the default long-running threshold

The following procedure sets the number of minutes used as the default long-running threshold. When a request has been running for longer than the set threshold, the request will be recorded as a long-running request and the NumLongRunningReq parameter will enter an alarm state. The out-of-box threshold setting is 120 minutes.

  1. Follow the applicationID (OA_SYSTEM) > CONC_REQUEST (OA_REQUEST) pathway.
  2. From the CONC_REQUEST (OA_REQUEST) menu, select the Setup > Long Running Threshold > Default Threshold command.
    The Long Running Threshold dialog box appears.
  3. Enter the threshold setting in minutes and click Accept. The default is 120 minutes.
  4. The default long-running threshold is now set. When a request exceeds this value, the NumLongRunningReq parameter will enter an alarm state.

To set thresholds for specific concurrent requests

You can assign a concurrent request its own customized long-running threshold setting that overrides the global default threshold. After you have assigned a customized threshold to a request, you can change its value. Use the following procedures to assign, modify and delete a threshold to and of an individual concurrent request. You can set the number of minutes desired as the long-running threshold. After you delete the customized threshold of a request, the concurrent request will take the default threshold as its long-running threshold. When a request has been running for longer than the set threshold, the request will be recorded as a long-running request and the NumLongRunningReq parameter will enter an alarm state. The out-of-box threshold setting is 120 minutes.

To add a long-running threshold for a specific concurrent request

  1. Follow the applicationID (OA_SYSTEM) > CONC_REQUEST (OA_REQUEST) pathway.
  2. From the CONC_REQUEST (OA_REQUEST) menu, select the Setup > Long Running Threshold > Add Threshold command.
    The List of First Characters dialog box appears.
  3. Select the first character of the concurrent request name to which you want to add a long-running threshold and click Accept.
    The List of Concurrent Programs dialog box appears, listing all requests starting with the selected letter.
  4. Select the concurrent request name to which you want to add a long-running threshold and click Accept.
    The Add/Change Long Running Threshold dialog box appears. This dialog box displays the default threshold setting as well as the maximum, minimum, and average running time of the selected concurrent request.
  5. Enter the desired threshold setting in minutes and click Accept.
    The customized long-running threshold for the selected concurrent request is now set. When this request exceeds the set threshold, the NumLongRunningReq parameter will enter an alarm state.

To change the customized long-running threshold of a specific concurrent request

  1. Follow the applicationID (OA_SYSTEM) > CONC_REQUEST (OA_REQUEST) pathway.
  2. From the  CONC_REQUEST (OA_REQUEST) menu, select the Setup > Long Running Threshold > Change Threshold command.
    The List of Concurrent Programs dialog box appears, listing all the concurrent requests whose long-running thresholds have been customized.
  3. Select the concurrent request name whose long-running threshold you want to change and click Accept.
    The Add/Change Long Running Threshold dialog box appears. This dialog box displays the default threshold setting as well as the maximum, minimum, and average running time of the selected concurrent request.
  4. Delete the number that appears in the Long Running Threshold field, enter the desired threshold setting in minutes, and click Accept.
    The customized long-running threshold for the selected concurrent request is now set to the newly set value. When this request exceeds the set threshold, the NumLongRunningReq parameter will enter an alarm state.

To delete the customized long-running thresholds of concurrent request

  1. Follow the applicationID (OA_SYSTEM) > CONC_REQUEST (OA_REQUEST) pathway.
  2. From the CONC_REQUEST (OA_REQUEST) menu, select the Setup > Long Running Threshold > Delete Threshold command.
    The Delete Concurrent Programs Selection dialog box appears, listing all concurrent requests whose long-running thresholds are customized.
  3. Select one or more concurrent request names whose long-running threshold you want to delete and click Accept.
    The Delete Concurrent Programs Confirmation dialog box appears, asking you to confirm the deletion of the selected concurrent request thresholds.
  4. Select the Are you sure? check box and click Accept; then click Exit.
    The customized long-running threshold for the selected concurrent requests has now been deleted and reset to the default threshold value. The default threshold setting is 120 minutes. When this request exceeds the set threshold, the NumLongRunningReq parameter will enter an alarm state.

To set the default long-pending threshold

The following procedure sets the number of minutes used as the default long-pending threshold. When a request has been pending for longer than the value set for this threshold, the request will be recorded as a long-pending request. The NumLongPendingReq parameter will enter an alarm status. The out-of-box threshold setting is 10 minutes.

  1. Follow the applicationID (OA_SYSTEM) > CONC_REQUEST (OA_REQUEST) pathway.
  2. Fom the CONC_REQUEST (OA_REQUEST) menu, select the Setup > Default Long Pending Threshold command.
    The Long Pending Threshold dialog box appears.
  3. Enter the threshold setting in minutes and click Accept. The default threshold setting is 10 minutes.
    The default long pending threshold is now set. When a request exceeds this value, the NumLongPendingReq parameter will enter an alarm state.

Related topics

Managing-bottlenecks

 

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