The db2diag.log can show entries like below
2014-08-14-04.15.02.177154-300 I92297A659 LEVEL:
Warning
PID : 41746466 TID : 15704 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-289 APPID:
111.123.45.67.12345.992233123456
AUTHID : USER1 HOSTNAME: server1234
EDUID : 15704 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, runtime interpreter, sqlriPEXInitHashTable,
probe:3194
DATA #1 : unsigned integer, 4 bytes
4
DATA #2 : unsigned integer, 4 bytes
2
DATA #3 : unsigned integer, 8 bytes
211817
DATA #4 : unsigned integer, 8 bytes
476851
DATA #5 : unsigned integer, 8 bytes
199379
2014-08-14-04.15.02.201086-300 E92957A527 LEVEL:
Warning
PID : 41746466 TID : 15704 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-289 APPID:
111.123.45.67.12345.992233123456
AUTHID : USER1 HOSTNAME: server1234
EDUID : 15704 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, runtime interpreter, sqlriPEXInitHashTable,
probe:3229
MESSAGE : .
The above warnings are normal behaviour which indicate that db2
could not get the ideal amount of sort memory at that point in
time, so it decided to use a reduced amount. Since these are
just normal warning messages, this db2diag.log entry will be
removed. The information about this form of post-threshold sort
is still available to users using the preferred monitoring
technique of using database monitor output.
For example: Using Partial early distincts threshold monitor
element
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.
ibm.db2.luw.admin.mon.doc/doc/r0058845.html |
