Process/query still running after job aborted
Posted: Fri Jan 10, 2014 10:12 am
We ran into an issue where a query was still running (for awhile) even though the job had been stopped (through the Director), query modified, and the job compiled and re-run. Any advice on how to avoid this in the future? There was an issue with this query - long running and so testing it outside of datastage would have helped, but besides that...does anyone have any advice to offer on it? Doesn't happen a lot but it did cause issues because it ran for awhile and database team didn't pick up on it until too late ![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)
![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)