This section outlines some basic monitoring regimes and methods for Oracle Utilities Application Framework applications. It is highly recommended that you read the Performance Troubleshooting Guides (Doc Id: 560382.1) on My Oracle Support.

During monitoring you are typically looking for unusual activity and seeing if the current configuration of the product can handle the peaks and troughs of usage.

Unusual activity is activity that is not representative of the normal activity. For example, maybe during a marketing campaign the call center traffic doubles. This would be regarded as unusual activity. At this point, the current configuration may not be configured to handle the traffic so the problem needs to be identified and the configuration changed to cater for the new load.

Also, during normal operations underlying problems may surface in the form of long running transactions, increases in error rates (in logs and timeouts) or runaway transactions. Runaway transactions are transactions that seem to be looping. These can be caused by data inconsistencies or bugs. Most of them are due to an unusual combination of data entries.

Some customers collect usage information to identity and analyze unusual activity. This is known as Site Profiling, Capacity Planning or Availability Planning. This is typically Proactive activity.

Oracle Utilities Application Framework applications store within the database usage information that can be extracted for this purpose. This section outlines the methods and techniques you can use to extract this information reactively and proactively.