The buttons on this toolbar represent the primary windows available for real-time monitoring. The buttons available depend upon the version of the Oracle database that is highlighted. If the first button on the context-specific toolbar was clicked, a Global window would be opened for the corresponding database on that server, displaying important statistics regarding the status of the Oracle instance. To begin monitoring, the DBA uses these pre-defied rules to easily adjust default values and collection intervals before turning on the rules to be monitored. The data must first be collected by the collector agent before data can be used by the analyzer or repository agent for the Event Management and Historical Repository features.
Historical data is retained in named stores, which have user-specified time intervals and duration.
An interval compression algorithm is used to minimize disk utilization. Data from the repository is used to obtain a historical perspective when the Surveillance Module's Event Management feature detects and alerts the DBA that conditions are occurring that are negatively impacting performance. Data from the Repository can be used to trend performance and space utilization data or the DBA could use the data to establish baselines for threshold values in Event Management's rule definitions. From these events, the system determines the actions that need to be taken. This process begins by defining and applying data rules in the Analyzer Agent.