Each DB2 timeout is reported in the system console log under message ID DSNT376I. If you have the ability to view your system console log, you can determine the users, plans, and resource involved in the timeout situation. Some interactive performance monitors can also provide the same type of information. You may prefer to use a routine to run against a copy of the console log and parse all of the DSNT376I messages found. The routine could run periodically, for example, every 24 hours, and report on that time period. You may want to sort the resulting information by database name to present a report usable by database administrators.
If your performance monitors provide timeout reports, determine what action is required to have the necessary data available. If the requirement is to run the DB2 Performance Trace 6, investigate how much overhead this will add to your DB2 subsystem. The cost may be worthwhile for severe timeout problems, especially if you run the trace only for a short period.
|
Copyright © 2013 CA.
All rights reserved.
|
|