Modifying the blackout configuration variable

Blackout periods set in PATROL Configuration Manager are not verified. To validate your changes you should set Blackout for one instance by using the Blackout menu command, then use the output for that variable in PATROL Configuration Manager to apply that blackout period to other instances.

When you create a blackout period for an instance using the Blackout menu command from an ORACLE or ORACLE_INSTANCE menu, the blackout information is stored in the /OracleConfig.blackout variable.

The value created for the variable contains the following information in the following format:
server_name day of the week start time in seconds after midnight duration of the blackout in minutes

For example, if you set a server called Oracle1 for a blackout period on Monday starting at 1:00 a.m. and lasting for 60 minutes, the following value would display for the /OracleConfig.blackout variable:
Oracle1 Monday 3600 60

You can change your blackout periods several ways:

• In a PATROL Developer Console, you can set your blackout periods by using the PATROL for Oracle*Blackout* menu command, test the blackout periods, import the modified variable into PATROL Configuration Manager, add the POKKMConfigUpdated rule to the rule set that contains the blackout rule, and deploy the new variable throughout your environment.
• In PATROL Configuration Manager, you can modify the example the rule set provided in the Blackout.cfg file installed with PATROL for Oracle, add the POKKMConfigUpdated rule to the rule set that contains the blackout rule, and deploy the modifications throughout your environment.

For more information about the Blackout feature in PATROL for Oracle, see Scheduling blackouts.

For a complete list of the values generated by variables, see pconfig variables.