Database Performance Analyzer
DPA has future monitoring data
DPA has charts for when it collects data that are in the same time as the DPA application server. If the application servers time zone or date is advanced to the future and then back monitoring stops until future data is past.
First published date
8/3/2021 3:18 PM
Last published date
6/23/2023 8:42 AM
Overview
The time zone and calendar of the application sever where DPA is installed are what is used in all charts. If something changes this to a date that is for example a month in the future and DPA collects data on monitored instances and then the date and time is set back monitors will simply shut down until that time has past.
In DPA the monitored instances will not connect and the log file will have a message like the following.
WARN (2021-07-29T21:42:32,750-0500) [databaseManager-thread-16] {name=example server DatabaseMonitor:### - Monitor for database [example server] failed to start due to [Ignite detected future monitoring data. This can occur when clock is set back or stats query ran long (>10min). Monitoring will automatically resume after [2023-08-28 18:09:59.0]. No action required by user.]. Will attempt to retry every [3840] seconds...
org.quartz.JobExecutionException: DatabaseMonitorStartJob failed
This is expected behavior.
In DPA the monitored instances will not connect and the log file will have a message like the following.
WARN (2021-07-29T21:42:32,750-0500) [databaseManager-thread-16] {name=example server DatabaseMonitor:### - Monitor for database [example server] failed to start due to [Ignite detected future monitoring data. This can occur when clock is set back or stats query ran long (>10min). Monitoring will automatically resume after [2023-08-28 18:09:59.0]. No action required by user.]. Will attempt to retry every [3840] seconds...
org.quartz.JobExecutionException: DatabaseMonitorStartJob failed
This is expected behavior.
Product section
Database Performance Analyzer
Resolution
First, check the Date and Timezone of the DPA server if it was modified or changed.
If yes, please change it back to the correct Timezone then Reboot the DPA server
If this date is too far in the future and you can't wait or have the monitoring down that long the best resolution is to restore to a database backup for the DPA repository to before the calendar or time zone change.
If yes, please change it back to the correct Timezone then Reboot the DPA server
If this date is too far in the future and you can't wait or have the monitoring down that long the best resolution is to restore to a database backup for the DPA repository to before the calendar or time zone change.
- Stop DPA on windows this is the service "Ignite PI Server" on linux run the ./shutdown.sh
- restore the database backup for the DPA repository to a time before the application server had it's time or date changed