Creating blackouts
You can use IBM® Db2® Data Management Console to create blackouts for blocking a database connection or disabling some of the functions such as monitoring and alerting.
About this task
There are three types of blackout:
- Full blackout - Disconnects databases from console.
- Monitor and alert blackout - Pauses monitoring and alerts for databases. The monitor does not collect metric data and the alert are not generated.
- Alert blackout - Pauses only alerts for databases. The alerts are not generated.
The blackout event can be performed and released by the blackout job.
For HADR and pureScale® connections, to blackout the whole HADR or pureScale connection profile, you need to trigger the blackout event against each member.
Note: When migrating blackouts from Data Server Manager to Db2 data Management console, the weekly and every day scheduled blackout job can be migrated successfully. Similarly, blackout jobs that are scheduled for one month and one day can be migrated successfully. All other blackout job schedules are not supported. After migration, you can check the log details to verify whether the blackouts were successfully migrated. Check the job log file located in ibm-datamgmtconsole/addons/job-scheduler/logs/nohup.out. If you find a log
similar to time="2021-05-28T09:20:40Z" level=info comp=JobScheduler msg="the job
BlackoutEvent_1 migrated from DSM has a not compatible schedule format 41 5 3 3,4 ?" in the log file, then it means all the blackout job data is migrated to Db2 Data Management Console repository database. But these blackout jobs are not displayed in UI because they are not supported in Db2 Data Management Console.
Procedure
To create a blackout period: