|
View previous topic :: View next topic
|
| Author |
Message |
vijikesavan
Active User
Joined: 04 Oct 2006
Posts: 118
Location: NJ, USA
|
|
|
|
Hi,
We have identified a long running job - around 10 hrs of elapsed time with 1.5 hrs CPU.
Running strobe showed that the maximum wait time is in
| Code: |
| DSNECP00 DSN START-UP CSECT - 98%. |
I found some strange messages in the Jes
| Code: |
| "<pgmname> <step name> WAIT TIME EXPIRED-REPLY CANCEL OR WAIT" |
I tried to run EXPLAIN on the SQL Statement, it showed error message
| Code: |
"DBG55160W SQL wait time limit exceeded.You can either increase
the SQL-WAIT-INTERVAL in SYSPARMS, or create shadow tables and/or
catalog indexes (DB2 V4 or higher) in order to make the query run
faster. " |
Is it refering to SYSIBM.SYSPARMS table? If yes, which column I need to set to increase the wait interval.
I need to run this query before tuning it. ( Am sure the SQL is inefficient)
Pls help.
Thanks,
Viji |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
I'd suggest you talk with your dba(s) about any changes to the processing environment.
If you post the problem query(ies) here someone may have suggestions without having the run statistics. |
|
| Back to top |
|
|
vijikesavan
Active User
Joined: 04 Oct 2006
Posts: 118
Location: NJ, USA
|
|
|
|
Thanks.
Yes I spoke to DBA and the wait time is due to the enormous data the cursor is trying to open.
we are looking at tuning the SQL now.
Thanks for your reply.
Viji |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
You're welcome.
Good luck 
d |
|
| Back to top |
|
|
|
|
