Configuration methods

PATROL for Oracle allows you to use different methods of configuration:

• Automatic configuration by loading and using ORACLE_AUTO_CONFIG.kml
• Batch configuration
• Configuration by using scripts
• Configuration by using the PATROL Configuration Manager rule sets

Each method requires the same information, but differ in their methods of configuration.

The PATROL console-based configuration allows you the most control and the most interactive configuration. The configuration is done in real-time, so any problems are discovered quickly. However, this means that you must enter the data for each instance interactively. This option is best for a small number of instances.

The ORACLE_AUTO_CONFIG application represents an automatic configuration feature. When this application is loaded, discovery identifies all of the instances that it can, except for those instances that are explicitly excluded and those that are already configured, and applies the configuration specified in a file to all instances on the host.

The Batch Configuration allows you to create a text file that contains the configuration information for the Oracle instances. After the file is completed and saved, the InstanceStatus parameter detects and runs the batch configuration text file during the next polling cycle. This allows for quick and unattended configuration, but any difficulties with configuration that arise require that you research the logs and revise the text file.

With the PATROL Configuration Manager rule sets method, you need to set the values for certain pconfig variables. When these rules are applied to an Agent, the Agent automatically configures all the instances for which the rule sets have been created. Any difficulties with configuration that arise require that you research the logs.

Configuring multiple Oracle installations on Microsoft Windows

If a Microsoft Windows computer has multiple Oracle for Microsoft Windows installations with different $ORACLE_HOME directories, you can do one of the following options to allow PATROL to monitor the instances:

• Use the same version of Oracle on both the local and the remote instance
• Use the highest version of Oracle on the local instance to communicate with the remote instance.