Modifying parameter properties

The following procedure for modifying parameters employs the strengths of the KM and PATROL Configuration Manager:

• Make changes in one instance through the parameter property dialog boxes.
• Test the changes in that instance to make sure that the changes operate as expected.
• Export the modified parameter changes to PATROL Configuration Manager.
• Deploy the modified parameter changes to other instances through the PATROL Configuration Manager.

This method takes advantage of the validations performed by PATROL for Oracle and gives you the opportunity to verify that the changes perform as expected before deploying those changes throughout your environment.

1. Navigate to the parameter properties for the parameter you want to change:
   • In the PATROL Console for UNIX, click Attributes and then Application Classes to open a list of the application classes. Select an application class, then click Attributes and then Parameters to open the list of parameters provided by the selected application class.
   • In the PATROL Console for Microsoft Windows, select the KM tree tab and expand the appropriate application class, then click Global and then click Parameters to open the list of parameters provided by the selected application class.
2. Right-click (Windows) or click (UNIX) the parameter you want to access the parameter properties.
3. To activate or deactivate a parameter, perform one of these actions:
   • (Windows) Select the General tab and select or clear Active.
   • (UNIX) Double-click the parameter, and select or clear Active.
4. To change the interval between polling cycles, perform one of these actions:
   • (Windows) Select the Scheduling tab, and change the polling time.
   • (UNIX) Click the parameter and change the polling time.
5. To change the alarm thresholds and disable the alarms, perform one of these actions:
   • (Windows) Select the Border, Alarm1, and Alarm2 tabs and make changes.
   • (UNIX) Click Alarm Ranges, and double-click Border, Alarm1, or Alarm 2, and make changes.
      You can also configure an EVENTSPRING rule to set alarm thresholds for ETSM application classes. For more information, see Configuring rules to set alarm thresholds.
6. Save the configuration by choosing File > Save Configuration.
7. Test the changes on the instance until you are satisfied that they are working.
8. Using the PATROL KM for Event Management, convert the parameters in the instance to a rule set in PATROL Configuration Manager.
    The rules that represent each parameter contain the ANYINST for the instance name. The ANYINST designation allows you to apply these changes to any instance without adding specific instance name.

9. Drag and drop the rule set to any other AgentHostName where you want the changes applied. 

   Warning

   Note

   The following rule forces the instance to apply parameter changes immediately: "/AS/EVENTSPRING/PARAM_SETTINGS/STATUSFLAGS/ paramSettingsStatusFlag" ={REPLACE = "2"} If you do not want the changes to take place immediately, change the 2 to a 1 or remove this rule and reinitialize the agent for the instance when you want to apply the changes. For more information, see the PATROL Configuration Manager User Guide.

 Configuring rules to set alarm thresholds

To configure an EVENTSPRING rule to set alarm thresholds for ETSM application classes whose tablespace history is set to ON:

"/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/ORACLE_ETSM_REGULAR_TBSP_INSTANCE/_ANYINST/PctUsed"

To configure an EVENTSPRING rule to set alarm thresholds for ETSM application classes whose tablespace history is set to OFF:

"/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/ORACLE_ETSM_REGULAR/ANYINST_/PctUsed"