|
View previous topic :: View next topic
|
| Author |
Message |
kranthikumarb
Active User
Joined: 02 Jan 2009
Posts: 115
Location: Hyderabad
|
|
|
|
Hi,
I searched the forum for this topic, although I found few, but didn't give me answer to my doubt. Can someone please help me with the below.
I have 2 jobs, one updates; other extract data from the table space.
The extract job has cursor that doesn't have any one of the below clauses
WITH UR
FOR FETCH ONLY.
Because both jobs run at the same time, I am getting a -911 on the extract job. So I was thinking of using UR in the select cursor. But the clients didn't want to see un committed data. So I was thinking of using FOR FETCH ONLY. Before using that I wanted to check the isolation level it is using. I submitted a command -DISPLAY DB(ZDXY0005) SPACENAM(TSXYX12) CLAIMERS when a long running select query is executing with "WITH UR" , "FOR FETCH ONLY" and with out any of these two. In all three instances the tabls space is in RW mode and the isolation level is (CS,C).
Surprising to see a CS,C when using WITH UR.
I can set the pred and successor conditions, but there are many reading jobs.
Prefer to do it via program.
Can someone help me am I doing something wrong in the display statement?
"FOR FETCH ONLY" - Is this same as WITH UR but will give committed data without locking any pages? |
|
| Back to top |
|
 |
kranthikumarb
Active User
Joined: 02 Jan 2009
Posts: 115
Location: Hyderabad
|
|
|
|
Oopsy.... I found the extract program already has "FOR FETCH ONLY" in the declare.
Now more problems  |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
It is NOT a good idea to extract data from a table while it is being updated. There is a strong possibility that the extract will contain incomplete or corrupt entries. . . |
|
| Back to top |
|
|
gylbharat
Active Member
.jpg)
Joined: 31 Jul 2009
Posts: 565
Location: Bangalore
|
|
| Back to top |
|
|
|
|
