-
Title
DB2 9.7 Diagnostic Log Error caused by ENV_GET_DB2_SYSTEM_RESOURCES -
Description
A DB2 9.7 environment is finding the following message in they Db2 diagnostic log.
LEVEL: Severe
PID : 17598 TID : 14069748391168
PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
DB : DBNAME
APPHDL : 0-60484 APPID: AC12971E.EA42
AUTHID : USERID
EDUID : 4724 EDUNAME: db2agent (WC036P01) 0
FUNCTION: DB2 UDB, WLM, sqlrwEnvGetDB2SystemResourcesBackend, probe:0
DATA #1 : Pointer, 8 bytes
0x00007ff6276e7e80The Foglight agent for DB2 are producing some errors in the DB2 Diagnotic logs caused by use of ENV_GET_DB2_SYSTEM_RESOURCES in 9.7 DB2 Next: Provided workaround, customer to confirm if fix should be provided
-
Cause
The Foglight DB2 cartridge calls the DB2 table function SYSPROC.ENV_GET_DB2_SYSTEM_RESOURCES periodically on the DB2 9.7 monitored database, for example, every five minutes if the sampling interval is set to 5 minutes. The db2diag.log file gets filled with such messages when the Foglight database agent is running. -
Resolution
WORKAROUND
Add a filter so prevent the alarms from the Diagnostic log
- Select one or more DB2 agents in the database dashboard
- Select Settings > Administration
- Select Diagnostic Log
- Select the Ignore List tab
- Add a Filter Name
- Change Severity to Function
- Add the Expression
.*sqlrwEnvGetDB2SystemResourcesBackend.* - The Enabled checkbox should be turned on
- Click the Set button
- Click the Save Changes button
- Return to the databases dashboard
- Clear the Fatal diagnostic alarms
RESOLUTION
Disable the collection to prevent the collection from writing to the Diagnostic log.
- Access the Collections area in the DB agent Administration
- Highlighting the OS DB2 General Process collection
- Click the edit button,
- Uncheck the enable collection checkbox,
- Click the set button,
- Click the save changes button.