Hi guys,
ERROR Abortion: "Parallel job reports failure (code 1)"
Anyone farmilar with this error? There isn't any special circumstances I am running the job. But these error occurs too often.
Thanks.
Search found 32 matches
- Thu Feb 23, 2006 12:21 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Parallel job reports failure (code 1) Job failure
- Replies: 2
- Views: 2263
- Tue Feb 21, 2006 3:13 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Iconv Oconv
- Replies: 7
- Views: 3774
Iconv Oconv
Alternatively you can use StringToDate(Input.link[1,4]:Inpu.Link[6,9],"%yyyy%mm%dd") to convert to date. Hi thanks kumar. I've also thought of this. However, i am still searching for a pre-default function that will add the days I want into the date. Date() + 1 doesn't seem to work. Thanks.
- Tue Feb 21, 2006 1:59 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Iconv Oconv
- Replies: 7
- Views: 3774
Iconv Oconv
Sorry guys I have a bad habit of not posting all my thoughts in a single post... here goes: What i wanted to do is this. I get a source: 200600212 First 4 fields - year next 3 - month last 2 - date This is in integer format and from a source file. I wanted to bring this into a transformer and use ic...
- Tue Feb 21, 2006 12:49 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Iconv Oconv
- Replies: 7
- Views: 3774
Iconv Oconv
Hi there, There's nothing new about this topic... Except I am super new to parallel jobs having just recently hop from server jobs. I tried doing something too simple that is : seq file -> transformer -> seq file. 1 field involved oni. Source seq file is type varchar and des file is type integer. I ...
- Thu Feb 09, 2006 7:13 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DB issue or DS issue?
- Replies: 11
- Views: 2429
DB issue or DS issue?
I am curious about this, why would you have two jobs running the sme sql? You have all ready done the work to pick the data up from the database, why do it again? Hi all, Thanks for the replies. To: Mr kwwilliams Makes sense, but given the current design... after each extraction when they're going ...
- Thu Feb 09, 2006 12:43 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DB issue or DS issue?
- Replies: 11
- Views: 2429
DB issue or DS issue?
Are you sure that the difference in the row counts can't simply be a result of the fact that the jobs run at different times against a table that is actively being written to? That would seem to be the obvious culprit here. Your conclusion that "the number of records extracted should be identi...
- Wed Feb 08, 2006 9:29 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DB issue or DS issue?
- Replies: 11
- Views: 2429
DB issue or DS issue?
There's not nearly enough information here to provide you with any coherent help. :? You haven't mentioned the database. You state the two SQL statements are "exactly similar"... are they similar or are they exactly the same? Is the table you are sourcing from being actively written to wh...
- Wed Feb 08, 2006 7:21 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DB issue or DS issue?
- Replies: 11
- Views: 2429
DB issue or DS issue?
I keep encountering these wierd errors. Have yet to determine the root cause. I have 2 jobs that extract information from a table using ODBC stage. Both have exactly similar SQL statements referring to the same table with the same conditions (Including similar date condition) hence number of records...
- Fri Jan 27, 2006 1:59 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Auto Clearing Status File With Jobs
- Replies: 13
- Views: 9559
Auto Clearing Status File With Jobs
I don't use the ODBC stage all that much... is there an option to do a 'Read Only' or dirty read type query from the source database? As you mentioned, that may solve this issue for you. Yups, there is an option in the Transaction Handling tab to set the reading as read uncommited/dirty read. Howev...
- Thu Jan 26, 2006 9:55 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Auto Clearing Status File With Jobs
- Replies: 13
- Views: 9559
Auto Clearing Status File With Jobs
You and Kumar are a little... out of sync. The 'deadlocks' Kumar mentions are within DataStage and are totally unrelated to the issue you are facing in your Informix database. Without intimate knowledge of your job design, it would be hard to say exactly what is going on. You are either running int...
- Thu Jan 26, 2006 8:04 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Auto Clearing Status File With Jobs
- Replies: 13
- Views: 9559
Re: Auto Clearing Status File With Jobs
Hi, in addition,
In order to overcome the problem I am having...
Issit recommended that I do read uncommited (Dirty read) from my source database?
What are the cons?
In order to overcome the problem I am having...
Issit recommended that I do read uncommited (Dirty read) from my source database?
What are the cons?
- Thu Jan 26, 2006 7:49 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Auto Clearing Status File With Jobs
- Replies: 13
- Views: 9559
Auto Clearing Status File With Jobs
Hi, To avoid deadlock, you can alter dead lock manager, in $DSHOME/dsdlockd.config as start=1 timer=900 res=0 log= The value of timer can be altered according to your needs. The frequency in which the locks need to be cleared. -Kumar Hi all, thanks for the advice. The reason why I brought this up i...
- Wed Jan 25, 2006 3:30 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Auto Clearing Status File With Jobs
- Replies: 13
- Views: 9559
Auto Clearing Status File With Jobs
Nick, DataStage does not inlude a programmatic call to clear the log file for a job; it can be done explicitly (and the methods have been posted here) if necessary, but it is preferable to use the purge settings to automatically clear aged log entries either by age or number of previous runs. Hi fu...
- Wed Jan 25, 2006 3:26 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Auto Clearing Status File With Jobs
- Replies: 13
- Views: 9559
postarea_Reject_Ref_Chk_Del_C
Nick, DataStage does not inlude a programmatic call to clear the log file for a job; it can be done explicitly (and the methods have been posted here) if necessary, but it is preferable to use the purge settings to automatically clear aged log entries either by age or number of previous runs. Yups,...
- Wed Jan 25, 2006 2:26 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Auto Clearing Status File With Jobs
- Replies: 13
- Views: 9559
Auto Clearing Status File With Jobs
Greetings all!
I was wondering if it's possible to create a job to clear status files for other jobs each time before running these jobs. Is this possible?
Thanks in advanced.
I was wondering if it's possible to create a job to clear status files for other jobs each time before running these jobs. Is this possible?
Thanks in advanced.