DTS job failure !!! - Plz help

Hi There,

I have around 10 DTS jobs which run every night. These jobs basically
copy data from views of a source DB to tables in a target DB. These
jobs have been failing quite frequently in the recent past. I have
checked and there are no contraint violations (like primary keys) in
the target DB. Most of the times I just start the job again and it runs
successfully.

The DTS job history does not give me any details and it says it exits
by code -1. I read online and have enabled SQL logging for the DTS jobs
today.

I want some suggestions if there are any best practices while creating
these jobs. And can you suggest what are the common reasons why DTS
jobs fail?

Thanks a lot for your reply!

.

Relevant Pages

  • Re: DTS job hang at ActiveX script steps
    ... The ActiveX tasks of those jobs in problem handle a variety of different ... As it seems the hang up is irrelevant to what the ActiveX tasks do, ... >> We have a set of scheduled DTS jobs which run OK for months on SQL2000 ...
    (microsoft.public.sqlserver.dts)
  • Re: DTS--> xp_cmdshell permission error
    ... >I have several DTS jobs owned by several users. ... made using the proxy account, so does the proxy account have permissions ... global community for SQL Server professionals ...
    (microsoft.public.sqlserver.dts)
  • Re: DTS job failure !!! - Plz help
    ... I have around 10 DTS jobs which run every night. ... I read online and have enabled SQL logging for the DTS ... And can you suggest what are the common reasons why DTS ...
    (microsoft.public.sqlserver.dts)
  • DTS Hanged When Scheduled
    ... I have a couples of DTS jobs set up for data import from Oracle to SQL server. ... However, when they are scheduled to run routinely in SQL server job agent, these jobs may OCCASIONALLY got hanged. ... However, when the DTS jobs are run manually, this scenario never appear. ...
    (microsoft.public.sqlserver.dts)
  • Re: Finally get to go from os390 2.10 to zOS 1.8
    ... As you say exits have to be looked at etc and those were the types of things that we ran into and all had been anticipated. ... One of larger issues we had with OEM is that at that time the didn't have a clue as to what release of their software would run with each IBM release. ... Out of 200+ jobs we had 8 jobs that failed. ... It turned out that there was a JCL DD DLM= that did us in Jes 2 changed the rules and it wasn'[t terribly clear if it was the converter interpreter or JES. ...
    (bit.listserv.ibm-main)