Technical Blog Post
Abstract
DB2 purescale : db2diag.log flooded with sqleSubRequestRouter messages
Body
2018-02-05-06.46.19.377039-300 I1133162A522 LEVEL: Warning
PID : 8454392 TID : 99314 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-559 APPID: x.x.x.x.x.x
AUTHID : auth01 HOSTNAME: hostname
EDUID : 99314 EDUNAME: db2agnts (SAMPLE) 0
FUNCTION: DB2 UDB, base sys utilities, sqleSubRequestRouter, probe:1374
DATA #1 :<preformatted>
Subagent aborting request execution due to interrupt
2018-02-05-06.46.41.159272-300 I1136823A522 LEVEL: Warning
PID : 8454392 TID : 61028 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-574 APPID: x.x.x.x.x.x.x
AUTHID : auth01 HOSTNAME: hostname
EDUID : 61028 EDUNAME: db2agnts (SAMPLE) 0
FUNCTION: DB2 UDB, base sys utilities, sqleSubRequestRouter, probe:1374
DATA #1 :<preformatted>
Subagent aborting request execution due to interrupt current level for db2diag.log
The messages are from db2agents edu, which might indicate a parallel sort that got interrupted. If you also see that the event dump grows exponentially resulting in system full or crash in db2 please engage db2 support immediately. We will need to find out who interrupted the sorts and why. Please retain the event logs for further investigation.
If not accompanied by any other problem in your database, it is just an informational warning message as it looks, letting us know that a subagent was interrupted by a process which was running with higher priority, which is a typical and expected behaviour in db2. The sqleSubRequestRouter() is called to route the sub-agent request to the proper server function based on the request type.
As it is a normal operation, you can ignore it. It is not an error or warning that needs your attention or action. It could be that applications are interrupted because some user closed a connection or a timeout limit was reached, etc.
There are 2 ways now to avoid the messages temporarily :
- Disabling INTRA_PARALLEL parameter may help to avoid the messages. This will have its impact on system performance, please check the link to make a decision whether to use this workaround or not : https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.admin.config.doc/doc/r0000146.html
- Set DIAGLEVEL to 2. This will only report errors and severe errors in db2diag.log. No warnings or informational messages will be shown. The default diaglevel is 3 which is ideal for db2 support’s analysis should a problem occur but if this issue is troubling you a lot, set the diaglevel to 2 and engage db2 support to investigate if there is a bigger underlying problem to this.
UID
ibm11140178