Has anybody ever experienced a batch job failure, where the Source Stage says that it's "Starting" and the Target stage is "Waiting".? After 6 hours, the job fails and there is nothing in the Director Log.
Thank you,
Datastage batch job failures
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 597
- Joined: Fri Apr 29, 2005 6:19 am
- Location: Singapore
Yes, after restarting the job, it always completes successfully.kandyshandy wrote:Does the job run if you run it manually? What is your job design?
The job design contains some data checking and a couple of look ups. It also goes through our firewall and the Vendor's Firewall as well. I am thinking that it may be running into some Network issue?
I have never seen this failure message for jobs that run within our Organization.
That smacks of a resource issue, probably on your source / vendor side. Can you go into a little more detail on your source and the "data checking" you are doing?Angelok wrote:Yes, after restarting the job, it always completes successfully.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Hi Craig,
The Source tables are located in an Oracle (9i) Database. Datastage connects through a DB_Link.
As far as the Data checking goes, it's very basic, just simple validations. Actually, most of the Datastage jobs are just straight pulls. The interface contains 18 jobs, and almost all have failed with the same message (81002), at one time or another over the past year.
Thank you,
Angelo
The Source tables are located in an Oracle (9i) Database. Datastage connects through a DB_Link.
As far as the Data checking goes, it's very basic, just simple validations. Actually, most of the Datastage jobs are just straight pulls. The interface contains 18 jobs, and almost all have failed with the same message (81002), at one time or another over the past year.
Thank you,
Angelo