Architecture
PATROL for Oracle Enterprise Database enables you to monitor Oracle standalone local and remote instance monitoring.
A typical architecture for PATROL for Oracle Enterprise Database as follows:
Local monitoring
Related topics
UNIX remote monitoring
Windows remote monitoring
Data collection details
- In local monitoring, PATROL for Oracle Enterprise Database starts a Java process. This Java process runs local queries from an Oracle database to produce a list of instances and databases.
- For remote monitoring, the Java process identifies where the remote server is running. Based on the operating system, the Java process creates a remote client connection. For Unix, the remote connection is an SSH channel. For Windows, the remote client connection is an SSH or WMI channel. The same process logic applies as local monitoring.
- In the first inventory poll, the Java process discovers the Oracle system (databases and table spaces) and creates the discovery tree for PATROL.
- After the discovery is complete, the Java collector starts collecting availability for the Oracle instances, databases and partitions. The default availability poll cycle is 1 minute. The Java process also starts to collect data performance, with a 5 minute poll interval. All of the poll cycles are configurable.
PATROL for Oracle Enterprise Database collector details
The following table lists different PATROL for Oracle Enterprise Database collectors and explains how they work:
Collectors | Description |
|---|---|
ConfigurationManager | Runs every 15 sec (default) and is responsible for checking if there was any change in the pconfig area. |
ChannelListener | Responsible for opening a channel. It starts a Java process and to listens to the Java channel for incoming data. |
AutoDiscovery | Runs force discovery. |