If exception processing indicates an application-related problem, which is typically indicated as an elapsed time problem for an application or a user, use Explain reports to determine the access path of the suspected plan. In addition, if necessary, generate Accounting traces by using the TOP subcommand option.
- If the Explain reports and the Accounting traces do not identify the reason for poor SQL performance, use SQL Activity reports for detailed information about the specific statement, such as scans or I/O per page set or sort specifics.
- If the Accounting traces indicate a locking problem, run Locking reports.
- If the problem seems to be with binds or DB2® utilities, run Utility Activity reports.
As with system-related problem determination, you can run a Record trace if none of these report sets provide adequate information.