(Included in CA UIM 20.1.0)
A new table maintenance_window_history will be created on installation/upgrade of maintenance_mode probe. Also the data from the maintenance_window will be dumped into maintenance_window_history. By default, the newly data written in the maintenance_window table will be written to maintenance_window_history table as well.
Introduced a new key "purge_maintenance_window_history_interval" in maintenance_mode.cfg in <setup> section which will delete expired windows from maintenance_window_history table. It is disabled by default.
To enable it, purge_maintenance_window_history_interval (a new configuration) is to be set to a whole integer in the maintenance mode probe configuration under setup (for example, 1, which means the task would run every one hour). If the task is run, all the expired maintenance window entries would get deleted. To disable the task, it has to be reset to -1. (Support Case: 01302475)
(9.02 HF4) Fixed an issue where spectrumgtw syncing of the maintenance schedules was causing sluggish UMP performance. (Support Case: 20042333)
(9.10 HF1 and 9.20 HF1) Fixed an issue in which users were getting duplicate maintenance schedules after Spectrum integration. (Support Case: 20045094)
Fixed an issue related to the unknown error when deleting robot from maintenance schedule. (Support Case: 20047617)
Fixed an issue with spectrumgtw syncing of maintenance schedules causing sluggish ump performance. (Support Case: 20042333)
Fixed an issue with the UMP Maintenance Schedules at wrong day/time. (Support Case: 1278720)
Fixed an issue with USM which throws an error when removing device from maintenance schedule. (Support Case: 20109406)
Fixed an issue where UIM is impacting Spectrum causing memory issues with model creations/deletions. (Support Case: 20046860)
A new background task is added which handles the maintenance schedules by adjusting the time. It is scheduled to run on startup and every 24 hrs by default, the time interval is configurable. To change the time interval, "handle_dst_interval" key should be set under the setup section. As an example, In order to schedule the task to run every 24 hrs, set as: "handle_dst_interval=24" (Support Case: 20280779,20094790,20098531