Hi,
I am having a dts 2000 package which is accessing oracle source and loading data into sql server .The package runs fine when ran individually or from designer.
But when it is scheduled into a job, the job is being shown as ran successfully whereas the package is not run or for sure the data is not loaded.
I looked into microsoft articles regarding this problem and found that this job will be run under the profile who started the SQL Server Agent.There is another job which is running properly whose owner is xxx. So i changed the owner of my job into xxx.
But still the same condition is prevailing, job is being shown as ran successfully while the data is not loaded.
Kindly help me on this.
Thanks and Regards
Arobind
Are you executing this DTS package via SSIS? If not, you're in the wrong forum as this is an SSIS forum. The DTS forum can be found here: http://groups.google.com/group/microsoft.public.sqlserver.dts/topics?lnk=srgIf in SSIS, make sure that you set the FailParentOnFailure to true.|||
The fact is that, job history is showing as job ran successfully.When i check the details also, package step got executed successfully message is coming.
|||Then your problem is within SQL Server Agent...the Job is being reported as Successfully run but the results indicate it actully does not run....
|||
Arobind Balakrishnan wrote:
The fact is that, job history is showing as job ran successfully.When i check the details also, package step got executed successfully message is coming.
Again, is this an SSIS package, or an older DTS package? This forum can help you only if it's an SSIS package.|||
this is a dts package only.Sorry to put it in SSIS as i didnt find any dts forum in msdn forum site.
|||Arobind Balakrishnan wrote:
this is a dts package only.Sorry to put it in SSIS as i didnt find any dts forum in msdn forum site.
Nope, I'm not sure that they even had MSDN forums when DTS was released. So they created a USENET newsgroup for DTS, which is the link I provided above. They felt it was important to segregate the two products.
I could be wrong on some of those points though.
No comments:
Post a Comment