content_image/998655.jpg content_image/998656.jpg
Figure 13 shows what might be wrong with the SQL. 

<img src='content_image/998655.jpg'>

Figure 14 shows the details of statement status, activity time, lock wait time, CPU used, client application name, application ID, who ran the SQL, and what were the set threshold values. 

<img src='content_image/998656.jpg'>

Based on the IBM Data Server Manager alert and recommendation, you can either terminate the SQL or adjust the threshold value to make sure that the SQL running time reflects the expected value. 

Similarly, there might be other reasons for the bad performance of the SQL, such as the statistics not being up to date. You might need to run runstats , update the tables, and perform a reorg to correct or improve the performance. 

