Hi,
Suddenly I checked in all server jobs in all project has limits to stop stage set 50 instead of no limit.
Please give suggestion to set again for no limit.
Suddenly all server jobs extract only 50 rows
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 30
- Joined: Wed Mar 24, 2004 1:28 am
Funny, my clients always ran theirs with a limit of 1, thousands of jobs over many years. There's no reason for a Server job to ever throw an error unless something is really wrong and it needs to stop. IMHO.
Now, how are you running them? Does it matter if they are started manually from the client side via Director or Designer or all these all scheduled or run via an Enterprise Scheduler or command like via a script or ... ?? Just trying to get a handle on where the limit might have gotten reset.
Now, how are you running them? Does it matter if they are started manually from the client side via Director or Designer or all these all scheduled or run via an Enterprise Scheduler or command like via a script or ... ?? Just trying to get a handle on where the limit might have gotten reset.
-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:
Server jobs can also be run with a row limit, looks like these have been set for the OP's project. The solution is to set these values to 0 ( = no limit ).
Parallel jobs can also be row limited if compiled in trace mode.
Parallel jobs can also be row limited if compiled in trace mode.
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.