SYSVIEW for DB2 : Resource limit information on Thread Resource Limit Facility History report
Article ID: 252392
Updated On:
Products
Issue/Introduction
Some threads were cancelled by DB2 Resource Limit Facility(RLF) and checking the Thread Resource Limit Facility History(option 6 > 6 > 14) it appears that the thread would be cancelled when reaching the 7M ASUTIME which is specified in the RLF table.
Instead it appears like it is being cancelled at 56.8% of the limit.
How can this percentage value be explained?.
Environment
Release : 20.0
Component : IDB2
Resolution
There could be multiple reasons why this does not appear to be accurate.
1. The Thread could have been cancelled while executing and that particular single thread could have had multiple DB2 calls and the last call statistics are being displayed there.
Note: Only successfully executed DB2 calls are counted for the percentage calculation.
2. If the thread is no longer processing a dynamic SQL, then the percentage applies to the last DB2 call that took place for a dynamic SQL. Note that in this case, the percentage is usually very low because the last call is usually an inexpensive one.
3. If the thread history says "NOT ACTIVE" that indicates that RLF was not active at the time the thread ran or perhaps the DB2 RLF field QTXAPREC is actually zero (in which case DB2 has not filled in the value).
Additional Information
Feedback
