Skip to Content

Monitoring alerts

Information collected from monitoring Oracle Applications alerts is contained in the OA_ALERT application. The OA_ALERT application is located in the OA_SYSTEM window and is represented by the ALERT icon.

This topic contains the following information:

Oracle Alert is a separate module that can be installed as part of the Oracle Applications system. Oracle Applications uses this method to monitor the applications system. Within the Oracle Alert utility are predefined alerts that you can customize within Oracle Applications. Oracle Alert gives you the flexibility needed to monitor business information the way you want. Exception monitoring will keep you informed and take action automatically as you define it. It is a very convenient tool to consolidate the system data.

Oracle Alerts allows the Oracle Applications system administrator to receive notification through a page or e-mail when certain defined conditions occur. In order for Oracle Alerts to run, one of the following background mail processes must be running:

  • Oracle Mail
  • UNIX Mail
  • VMS Mail

If you are running Oracle Alerts, when you set up BMC PATROL for Oracle e-Business Suite, you must enter the background mail process that Oracle Alerts is using. If you are not running Oracle Alerts, the setup field is optional and you are not required to enter the background mail process. See Adding Oracle Applications server configuration for more information.

PATROL monitors the following information:

  • alert mail process
  • event exceptions

Monitoring the alert mail process

PATROL verifies that the alert mail process is running that was entered during KM setup. The AlertMailStatus parameter allows you to monitor the status of the mail process. PATROL automatically reports when the alert mail process is down. If there is only a single console connection, the dialog box prompts you to automatically start the alert mail process, requesting the root password. If there are multiple console connections, use the following procedure to restart the alert mail process manually.

To monitor the alert mail status

The AlertMailStatus parameter in the ALERT (OA_ALERT) application enables you to monitor the status of the mail process that Oracle Applications uses.

To start the alert mail process

  1. Follow the applicationID (OA_SYSTEM) > ALERT (OA_ALERT) pathway.
  2. Select the Admin Tool > Start Alert Mail Process command from the ALERT (OA_ALERT) menu. The Root Password dialog box appears.
  3. Type the root user name and password.
  4. Click Accept. The alert mail process starts running.

To monitor the work flow mailer status

The WorkFlowMailStatus parameter in the ALERT (OA_ALERT) application enables you to monitor the status of the work flow mailer process on a designated node:

Monitoring event exceptions

Event exceptions immediately notify the user of a database event as it happens. Oracle Applications users can define the database event, and Oracle Alert informs the user when it happens. Users can modify the predefined alert conditions or simply create their own, and Oracle Alert can send messages or perform predefined actions.

A group of parameters help to monitor event exceptions. You can monitor the following types of exceptions:

  • event exceptions
  • periodic exceptions
  • duplicated exceptions
  • no response exceptions
  • invalid response exceptions

To monitor event exceptions

Two parameters in the ALERT (OA_ALERT) application enable you to monitor event exceptions that occurred since the last collection. The value shown in the parameter will be the difference between the value received from the first polling cycle and the value received from the second polling cycle.

  • NumEventExp
  • ListEventExp

To monitor periodic exceptions

Periodic exceptions report key information according to a user-defined schedule. Oracle Applications users can modify the predefined alert conditions or simply create their own, and Oracle Alert can send messages or perform predefined actions according to the schedule set. Periodic exceptions can be set to run on demand or as often as needed during a daily, weekly, or monthly period.

Two parameters in the ALERT (OA_ALERT) application enable you to monitor periodic exceptions that occurred since the last collection. The value shown in the parameter will be the difference between the value received from the first polling cycle and the value received from the second polling cycle.

  • NumPeriodicExp
  • ListPeriodicExp report

To monitor duplicated exceptions

A duplicated exception occurs when the same alert information is received from more than one polling cycle and the same alert is sent more than once. PATROL monitors duplicated exceptions and provides information in the form of parameters.

Two parameters in the ALERT (OA_ALERT) application enable you to monitor duplicated exceptions that occurred since the last collection. The value shown in the parameter will be the difference between the value received from the first polling cycle and the value received from the second polling cycle.

  • NumDupExp
  • ListDupExp

To monitor no response exceptions

Some alerts require a response from the user. A No Response exception occurs if the user does not perform the required actions in response to an alert within a specified period of time. PATROL monitors No Response exceptions and provides information in the form of parameters.

Two parameters in the ALERT (OA_ALERT) application enable you to monitor duplicated exceptions that occurred since the last collection. The value shown in the parameter will be the difference between the value received from the first polling cycle and the value received from the second polling cycle.

  • NumNoResponseExp
  • ListNoResponseExp

To monitor invalid response exceptions

Some alerts require a response from the user. An Invalid Response exception occurs when the user responds to an alert within a specified period of time, but the user response is not in the defined format, and the alert cannot interpret the response. PATROL monitors Invalid Response exceptions and provides information in the form of parameters.

Two parameters in the ALERT (OA_ALERT) application enable you to monitor duplicated exceptions that occurred since the last collection. The value shown in the parameter will be the difference between the value received from the first polling cycle and the value received from the second polling cycle.

  • NumInvResponseExp
  • ListInvResponseExp

 

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