Bug-ID-Nummer |
BUG-000175372 |
Eingereicht | March 26, 2025 |
Zuletzt geändert | August 27, 2025 |
Gilt für | ArcGIS Monitor |
Gefunden in Version | 2024.1.1 |
Betriebssystem | Windows OS |
Betriebssystemversion | N/A |
Behoben in Version | Server 2025.0 |
Status | Fixed
Der Bug wurde behoben. Weitere Informationen finden Sie ggf. unter "Behoben in Version" und unter "Zusätzliche Informationen".
|
Workaround
- Shutdown ArcGIS Monitor.
- Take snapshot of ArcGIS Monitor Server.
- Create a database backup for good measure.
- Generate CREATE scripts of views that use metrics data (alerts_view, metrics_data_view, metrics_view).
- To generate scripts you would
- log into pgAdmin4.
- Expand the Monitor Database.
- Expand Schemas.
- Expand views.
- Right click the desired view (alerts_view, metrics_data_view, metrics_view).
- Copy the script from the new window to Notepad or Notepad++
- Drop above views that depend on metric_id (alerts_view, metrics_data_view, metrics_view).
- ALTER TABLE metrics ALTER COLUMN id TYPE BIGINT.
- ALTER TABLE metrics_data ALTER COLUMN metric_id TYPE BIGINT.
- ALTER TABLE alerts ALTER COLUMN metric_id TYPE BIGINT.
- ALTER sequence metrics_id_seq as bigint MAXVALUE 9223372036854775807.
- Recreate views previously dropped.
- Restart ArcGIS Monitor.
Please reach out to Marlon A. or Marlon S. for any clarification.
Schritte zur Reproduzierung