Troubleshooting
Problem
Why does DB2 health indicator report an impossibly high HADR log delay?
Symptom
db2diag.log contains errors similar to the below:
2016-08-11-03.05.06.214982 Instance:db2abc Node:000
PID:24838290(db2acd 0) TID:772 Appid:none
Health Monitor HealthIndicator::update Probe:500
ADM10500E Health indicator "HADR Log Delay" ("db.hadr_delay") breached
the
"upper" alarm threshold of "15 Minut" with value "9223372036854775807
Minutes"
on "database" "db2uwpsu.WPSUSCH ". Calculation:
"(db.hadr_log_gap*var.refresh_rate/60)DIV(delta(db.
hadr_secondary_log_pos));" =
"(((38 * 1800) / 60) DIV (18458938620 - 18458938620))" =
"9223372036854775807
Minutes". History (Timestamp, Value, Formula): " (08/11/2016 02:35:
06.464063,
0, (((0 * 1800) / 60) DIV (18458938620 - 18458938620))), (08/11/2016
02:05:05.915347, 0, (((0 * 1800) / 60) DIV (18458938620 -
18458938620))),
(08/11/2016 01:35:06.442787, 0, (((0 * 1800) / 60) DIV (18458938620 -
18458938620))), (08/11/2016 01:05:06.001012, 0, (((0 * 1800) / 60) DIV
(18458938620 - 18458938620))), (08/11/2016 00:35:05.462085, 0, (((0 *
1800) /
60) DIV (18458938620 - 18458938620))), (08/11/2016 00:05:05.924495, 0,
(((0 *
1800) / 60) DIV (18458938620 - 18458938620))), (08/10/2016 23:35:
06.155896, 0,
(((0 * 1800) / 60) DIV (18458938620 - 18458938620))), (08/10/2016
23:05:05.666349, 0, (((0 * 1800) / 60) DIV (18458938620 -
18458938620))),
(08/10/2016 22:35:05.953605, 0, (((0 * 1800) / 60) DIV (18458938620 -
18458938620)))
(db.hadr_log_gap*var.refresh_rate/60)DIV(delta(db.
hadr_secondary_log_pos))
delta(db. hadr_secondary_log_pos) = 18458938620 - 18458938620 = 0.
We get in the exception case of division of zero, and
9223372036854775807 Minutes = 17548272520652.160156 YEARS
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
30 April 2025
UID
swg21995856