Monitoring availability


Information collected from monitoring the general availability of specified Oracle Applications instances is contained in the OA_AVAILABILITY application. The OA_AVAILABILITY application is located in the OA_SYSTEM window and is represented by the AVAILABILITY icon.

This topic contains the following information:

BMC PATROL for Oracle e-Business Suite provides you with parameters that monitor the availability of Oracle Applications instances. You can specify the time period during which you want BMC PATROL for Oracle E-Business Suite to monitor the application and database errors. The graph parameters count the number of errors that were found in the database or the applications during the specified period. The text parameter lists all errors that were found in that same period. You can acknowledge errors found during the specified time period. BMC PATROL for Oracle e-Business Suite will ignore the acknowledged errors until the specified time period ends.

In addition, you can select the parameters for which you want to have annotated data points. See Data point annotation for more information.

Monitoring Oracle Application Status

Using the OAStatus parameter allows you to monitor the status of the Oracle applications. This status is a combination of DbStatus, SqlNetStatus, Concurrent managers, Forms server, Web server, Metrics Server and Metrics Client. When the parameter enters an alarm state, the recovery action of the responsible listener reports that the listener is down.

The OAStatus parameter in the AVAILABILITY (OA_AVAILABILITY) application enables you to monitor the status of the Oracle applications.

Monitoring Database and Application Errors

A group of parameters and a report help to monitor database and application errors. You can review the database and application errors during a specified time period.

To review database and application errors that occurred during the last cycle

Three parameters in the AVAILABILITY (OA_AVAILABILITY) application enable you to review database and application errors that occurred during a specified time period.

  • NumAppError
  • NumDBError
  • ListDBAppError

To set the time interval for database and application error monitoring

  1. Follow the applicationID (OA_SYSTEM) > AVAILABILITY (OA_AVAILABILITY) pathway.
  2. Select the Error Display Window command from the AVAILABILITY (OA_AVAILABILITY) menu. The Error Display Window appears.
  3. Determine the time span for which you want errors to be displayed and type the number of days in the Days field and/or select the number of hours and minutes in the Hours field. The default value is 1 day.
  4. Click Accept.

The time span is set. Every time you set up the time span, it is immediately put into effect for a limited, user-defined length of time. The parameters NumAppError, NumDBError, and ListDBAppError will display the number of application and database errors occurring during this specified time span.

Acknowledging Database and Application Errors

Use this procedure to acknowledge database and application errors. When database or application errors occur, either the NumAppError or the NumDBError parameters count the number of errors occurring during the time span determined in the error display window.

If you do not want the parameters to count certain errors, you can acknowledge the desired errors, and the parameters will not count the error and the error will not appear in the ListDBAppError parameter during the time span determined in the error display window.

To acknowledge database and application errors from a specified time span

  1. Follow the applicationID (OA_SYSTEM) > AVAILABILITY (OA_AVAILABILITY) pathway.
  2. Select the Acknowledge Error command from the AVAILABILITY (OA_AVAILABILITY) menu. The Acknowledge Errors dialog box appears, listing all database and application errors that occurred during the time span determined in the error display window.
  3. Select the errors you want to acknowledge.
  4. Click Accept.

The acknowledged errors will not be counted by the NumAppError or the NumDBError parameters and will not appear in the ListDBAppError parameter during the time span determined in the error display window.

 

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