Datastage Px job Process id getting failed automatically
Moderators: chulett, rschirm, roy
Datastage Px job Process id getting failed automatically
Hi Friends,
I am facing a peculiar problem while running a datastage job.The job loads data from sequential file to Oracle db and there is reject link after the oracle stage.The volume of data is 1.8 million.Its just 1-1 job.The norma; elapsed time for this job is 45 min.When I try to run this job,it goes fine until sometime after that data also gets loaded to some extent then automatically in director log we will see Process id failed for this job. And we cannot view this job in director any more but I can view the job in designer and director.This problem occurs frequently for only this job.After that I re import the job from Pre-prod to Prod then it works fine.can anybody provide some solution for this?
Many thanks in advance,
I am facing a peculiar problem while running a datastage job.The job loads data from sequential file to Oracle db and there is reject link after the oracle stage.The volume of data is 1.8 million.Its just 1-1 job.The norma; elapsed time for this job is 45 min.When I try to run this job,it goes fine until sometime after that data also gets loaded to some extent then automatically in director log we will see Process id failed for this job. And we cannot view this job in director any more but I can view the job in designer and director.This problem occurs frequently for only this job.After that I re import the job from Pre-prod to Prod then it works fine.can anybody provide some solution for this?
Many thanks in advance,
Re: Datastage Px job Process id getting failed automatically
Hi,
I think so , when you r using reject link to oracle stage the sql code column automatically will genarate. so that you need drop that sql code column by using modify stage. then it works fine.
I think so it will help you .
Let me know once you try this.
Cheers..................!!!!
I think so , when you r using reject link to oracle stage the sql code column automatically will genarate. so that you need drop that sql code column by using modify stage. then it works fine.
I think so it will help you .
Let me know once you try this.
Cheers..................!!!!
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
Load type is just Insert and no update.....ArndW wrote:What method are you using in your Oracle stage - upsert or load? Does the job fail at the same place each time?
Also, you writethen writeAnd we cannot view this job in director any moreso I am unclear as to what you mean.but I can view the job in designer and director
I will be able to see the job design in designer as well as manager ..but I cannot see the job in Directorshreya27 wrote:Load type is just Insert and no update.....ArndW wrote:What method are you using in your Oracle stage - upsert or load? Does the job fail at the same place each time?
Also, you writethen writeAnd we cannot view this job in director any moreso I am unclear as to what you mean.but I can view the job in designer and director
Warnings are due to datatype conversions...One more thing..there will be so many warnings that most of the times when I try to open the log for this job...datastage server will get hanged and will never open the logs...ArndW wrote:Let us just do one issue at a time. What sort of warnings are you seeing? Please cut-and-paste a sample to the thread. ...
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
Target table is loaded with 1.2 million records out of 1.8 million.....other records get rejected because of upsert failure...Sainath.Srinivasan wrote:Try to resolve your warnings first.
Do you get any rows in your target table ?
Ask your DBA to monitor the load and check for any hanging or defunct process in Oracle (especially if they are sti ...