×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC PATROL for Oracle Database Monitoring 9.7 ... Using Using in BMC PATROL environment Using PATROL Configuration Manager to modify and migrate configuration

Using the rule and rule set examples

Some of the rules and rule sets that are installed when you install PATROL for Oracle are required: POKKMConfigUpdated and the POKKMConfigInstanceRemoved (see Using the ConfigUpdate parameter) trigger the ConfigUpdate parameter, and provide a way for you to manage the parameters.

All of the other rules and rule sets installed with PATROL for Oracle are examples that you can use as an example of how that particular rule or rule set should appear.

Warning

When you make changes to a KM by directly modifying rules and rule sets in the PATROL Configuration Manager, no validations are performed. Alternatively, if you make changes by using the menu commands and parameter property dialog boxes provided by the KM, the values you enter are validated by the KM.

Note

If the example rule set does not contain the POKKMConfigUpdated rule, you must add the POKKMConfigUpdated rule before applying the rule set to an instance.



The following are the optional rules and rule sets installed with PATROL for Oracle and a short description for each:

  • Blackout.cfg provides examples for the blackout variable. For more information about Blackout, see Modifying the blackout configuration variable.
  • ConfigUpdate_Activate.cfg activates the ConfigUpdate parameter. It is active by default, but if you deactivated the ConfigUpdate parameter, you can reactivate it globally using this rule.
  • ConfigUpdate_DeActivate.cfg deactivates the ConfigUpdate parameter. The ConfigUpdate parameter is active by default. You can use it to deactivate it throughout the enterprise, and use ConfigUpdate_Activate.cfg to reactivate.
  • DisableListener.cfg provides a rule that you can use to disable a listener.
  • EnableListener.cfg provides a rule that you can use to enable a listener.
  • GlobalParams.cfg provides all of the Oracle parameters in rules that you can use to modify parameter settings and apply to any instance.
  • ModifyInstance.cfg provides rules that you can use to change the Always Online and Categories configuration variables.
  • PcmConfig.cfg provides a set of rules that you can use to configure an instance for monitoring. For more information about this configuration method, see PATROL Configuration Manager (PCM) rule sets configuration.
  • Remove_All_ConfigInstance.cfg provides a rule that you can use to remove all configured instances.
  • Remove_One_ConfigInstance.cfg provides a rule that you can use to remove one configured instance.
Was this page helpful? Yes No Submitting... Thank you
Last modified by Confluence Admin on Mar 10, 2014

Comments

Log in or register to comment.

Moving rule sets to the PATROL Configuration Manager directory
Using PATROL Configuration Manager to change the default database password
© Copyright 2014 - 2018, 2022 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.