Lately I have had DB2 Admins breathing down my neck because users are creating some pretty intense queries causing DB2 to do hefty summarizations. What I would like is that when a governor is tripped, that the DB2 Query is killed. Currently that does not happen. Does anyone have some insight on how to clean up these queries?
governance via solutions like db2gov is one approach the other is to consider DB2 WLM rules to allow the 'mail to arrive' just slower.
of course the last is to review what the users do and how to help DB2 response faster via MQTs, statistical views etc to improve the planning and execution etc.