I am using container as lookup . if no rows are returned from container . the job is running for infinite time .
pls suggest what to do.
Thanks
sun.
container as lookup. if no rows are returned .......
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
I assume you are trying to perform a query / reference to a table in your container. Check whether you are updating any rows if it does not exist. This may cause dead-lock and be the reason for the infinite delay.
If the above is the case, ask your DBA to monitor the RDBMS activities during your job run.
If the above is the case, ask your DBA to monitor the RDBMS activities during your job run.
Re: container as lookup. if no rows are returned .......
There must be something else going on. The simple fact that a lookup in a shared container returns no rows shouldn't cause something like this.sun786 wrote:I am using container as lookup . if no rows are returned from container . the job is running for infinite time .
![Confused :?](./images/smilies/icon_confused.gif)
We'd need a better idea of exactly what's going on in your shared container and how you are using it in the job to be able to provide more help.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers