IBM Mainframe Forum Index
Log In
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register

Difference between time spent on OPEN vs FETCH

IBM Mainframe Forums -> DB2
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message

Active User

Joined: 05 Jun 2009
Posts: 185
Location: Planet Earth

PostPosted: Fri Oct 25, 2013 11:52 pm
Reply with quote

Hi all,

We are in the process of trying to reduce the run time of long running batch jobs. We used APA to profile the long running steps. The APA reports shows a high CPU and Wait time on FETCH statement of a dynamic cursor. The corresponding OPEN statement consumption is <10% of the total consumption of FETCH statement.

I am trying to understand the difference between the time spent on the OPEN and FETCH. Does this mean that the cursor was resolved faster (as the OPEN only took 10% of the time) ? Will this imply that implementing multi row fetch (which might reduce the total number of database calls) improve the performance of this fetch statements ? Or will I still have to go ahead with fine tuning the query to improve its access path ?

Please advice/guide me on which would be the best approach.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus

Joined: 23 Nov 2006
Posts: 19245
Location: Inside the Matrix

PostPosted: Mon Oct 28, 2013 12:29 am
Reply with quote


From what little has been posted, I cannot make a suggestion about which would be better.

You need to provide much more detail.

How was the 10% determined? What about the result of an explain?

Is the test environment like the prod environment as far as volume and table/key definition?

Keep in mind that different Opens require more resources.
Back to top
View user's profile Send private message

Senior Member

Joined: 11 Aug 2009
Posts: 1281
Location: Belgium

PostPosted: Mon Oct 28, 2013 1:02 pm
Reply with quote

If the query involves an intermediate resultset, then it is resolved at OPEN . If not then each FETCH is taking CPU.
If all qualifying rows are being searched (and sorted) before the first row can be returned, it will be the OPEN that takes time.
If rows can be returned to the program as soon as DB2 finds them, then the FETCH will take the time.

Note that not all ORDER BY/GROUP BY cause an intermediate resultset, some/most are resolved by using the correct indexes.
Not using an order by or group by does not mean there will be no intermediate rseultset. it all depends on the accesspath.
Back to top
View user's profile Send private message
Ed Goodman

Active Member

Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Mon Oct 28, 2013 7:22 pm
Reply with quote

Is there any chance that during the APA measurment session, the open was done only once, while the fetch was done thousands/millions of times?

This would result in a skewed view of the percentages.

ie, a FETCH that is taking 1/1000 the CPU of an OPEN would show as equal CPU if it ran 1000 times during the measurement.

When you look at the overall cpu/wait for he entire job, where is your problem?
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DB2


Similar Topics
Topic Forum Replies
No new posts To pull the file with Date and Time u... TSO/ISPF 17
No new posts DFSORT to add 6 hours to time(tdate-t... DFSORT/ICETOOL 16
No new posts Difference between VALIDPROC and CHEC... DB2 3
No new posts UUID4 - extracting time element COBOL Programming 1
No new posts Cobol-db2 : SQL query is running for ... DB2 4
Search our Forums:

Back to Top