hi, i am facing a similar issue. My DS is running on 4 nodes. I have specified 2 sessionperplayer and hence 8 requested sessions. stil i am getting this warning when there are no records to be fetched :
Delete,0: Query returned no results. No read will be performed.
Delete,0: Query returned no results.
Moderators: chulett, rschirm, roy
Rather then jump on the end of an eight year old topic let's get you into one of your own.
What database is this?
What database is this?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
My solution is to use a prior server job to determine whether there are any rows to process. This job stores the count of rows to be processed in its user status area, which drives a custom trigger ($UserStatus > 0) to determine whether the next job runs or not.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Let me walk you through my job design.
I have 3 TD enterprise stages in one parallel job which run different queries parallely and i am combining the output using a funnel in a file.
With your solution, the prob is, i will have to check the output for all the three queries and run them accordingly(seperate of each other).
Can't we remove the warnings at all?
I have 3 TD enterprise stages in one parallel job which run different queries parallely and i am combining the output using a funnel in a file.
With your solution, the prob is, i will have to check the output for all the three queries and run them accordingly(seperate of each other).
Can't we remove the warnings at all?