DSXchange

bvishwanathr

Hi, I wanted to get a clarification regarding the SortMerge Collector method. Here is what I intend to do in my job : I want to combine/merge four sorted input files having the same column definition into one sorted output file i.e, the output file should be fully sorted. I am sure there are multipl...

bvishwanathr

I understood that there is something to do with my key columns in the lookup stages. We are actually renaming the column name "DC_TRLR_D" to another name and another column "ACCT_D" to "DC_TRLR_D" in the lookup stage. I have found the workaround for my problem. In the ...

bvishwanathr

bvishwanathr wrote: I understood that there is something to do with my key columns in the lookup stages.

We are actually renaming the column name "DC_TRLR_D" to another name and another column "ACCT_D" to "DC_TRLR_D" in the lookup stage.

bvishwanathr

bvishwanathr Just rename the job compile and run it that should solve your problem, do let us know if it really works in you case as well. No, It doesnot work. I understood that there is something to do with my key columns in the lookup stages. We are actually renaming the column name "DC_TRLR...

bvishwanathr

DSguru2B wrote:Just for debugging purposes, if you make the job "not readonly" and "not protected" in the new environment and re-run it, do you still see this error?

Yes, I still see the error

bvishwanathr

I have a strange situation with my datastage parallel jobs and i dont have any idea how to go about the problem. Following are the details: There are couple of jobs which are running on our production server(protected) successfully but the same jobs when imported to a different server and are run, w...

bvishwanathr

Hi, I'am also facing the same kind of a problem. Following is the error message we get : "main_program: Fatal Error: Source "DC_TRLR_D" is already kept." Till date we havenot seen this error in our development region , the same job runs fine in our production environment. Even if...

bvishwanathr

did you do a searh on this error code here? i got 121 results. start with this one: http://www.dsxchange.com/viewtopic.php?t=98717&highlight=141 It saya this error code is when DS is not able to log into UV. Well i did see the error codes in the include files, but i dont think return code 141 i...

bvishwanathr

chulett wrote:What version are you running? Have you contacted Ascential support and asked them this question? ...

Version : 7.5.1

We did not contact Ascential Support, will do that !!

bvishwanathr

I've seen this '141' return code from dsjob in the past, even when using the -jobstatus option. It used to crop up occasionally, and from what I recall it was only from a Sequence job that had actually Finished OK. I also think it only happened with Sequence jobs that used the Wait For File stage. ...

bvishwanathr

We have a job sequence which contains some 10-12 jobs set to execute one after the other. We run the sequence from a script using the dsjob command: $DSHOME/bin/dsjob -run -wait -param $APT_CONFIG_FILE=/apps/Ascential/DataStage/Configurations/FO_4_Node_Prod.apt -param jp_ProcessingDir=/work/PSA/proc...

DSXchange

Search found 11 matches

SortMerge Collector

main_program: Fatal Error: Source "<Field> is alr

dsjob returns 141, when does this happen?