|
Problem IT29792
|
Status: Closed |
INCORRECT VALUE OF NUM_COORD_AGENTS RETURNED WHEN QUERIED BY FUNCTION TABLE MON_GET_DATABASE
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The NUM_COORD_AGENTS metric somethimes went negative when
queried by
MON_GET_DATABASE , for example :
db2 "select current_timestamp as SNAPTIME , D.num_coord_agents
from (select * from TABLE(MON_GET_DATEBASE(-2))) D"| more
SNAPTIME NUM_COORD_AGENTS
2019-07-11-15.02.01.344802 4294958122
2019-07-11-15.02.01.344802 4294958142
2019-07-11-15.02.01.344802 4294958045
2019-07-11-15.02.01.344802 4294958148
2019-07-11-15.02.01.344802 4294957821
2019-07-18-18.21.38.267017 17
2019-07-18-18.21.38.267017 18
2019-07-18-18.21.38.267017 13
2019-07-18-18.21.38.267017 13
2019-07-18-18.21.38.267017 4294967124
2019-07-18-18.21.38.267017 4294965028
While , the other function table MON_GET_INSTANCE returns the
expected correct value of num_coord_agents
db2 "select current_timestamp as snaptime , D.num_coord_agents
from (select * from TABLE(MON_GET_INSTANCE(-2))) D"| more
SNAPTIME NUM_COORD_AGENTS
2019-07-11-15.02.24.136198 18
2019-07-11-15.02.24.136198 18
2019-07-11-15.02.24.136198 19
2019-07-11-15.02.24.136198 18
2019-07-11-15.02.24.136198 18
2019-07-18-18.22.42.195529 17
2019-07-18-18.22.42.195529 17
2019-07-18-18.22.42.195529 18
2019-07-18-18.22.42.195529 13
2019-07-18-18.22.42.195529 13
2019-07-18-18.22.42.195529 83 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Incorrect monitor metrics of num_coord_agents *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* reactivate db *
**************************************************************** |
| Local Fix: |
deactivate the db and then re-activate it |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.07.2019
05.07.2020
05.07.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
