DSXchange

Hi nivaskvs: Do you have any reference name for this patch? We are seeing the same problem with our PX jobs. Job would fail without any apparent reason but aborts with this error: main_program: Unexpected termination by Unix signal 9(SIGKILL). Upon rerunning the job, it executes fine. What is the l...

What is the value of PWD, try with '.'.

Another good new is, Your support provided might have the workaround for this. You can ask for ExecSilentSh().
There are some work arounds as well. The same has be discussed. Pls do a search.

Count the number of records of the input file and pass as a parameter.
In the transformer, using stage variable, create a counter for each record that goes to reject. If the counter is greater than the parameter value, so what ever you need.

View the input data in a test viewer(Hex editior).
Check whether you got some special character as end of record.
Also check the setting in the sequintial satage, about recored delimeter.

If it is character trim should work.
Else If your field length is 2, then try
If (A.code= "C ") Then "THis C" Else If (A.code= "P ") Then "This is P" Else "This is CP"
Space after "C " and "P "

Is both the run with same user id?
Is that file been accessed parallely?

Try with adding some DefaultNullableValue to that field as 0s.

What is the input and what is the desired output?
If the input is given as 2006, do you want to convert it as 01-01-2006 or 31-12-2006?

What is the command been wrapped in Wrapper stage?

Is your both source and target are in same database?
What difference it makes if you replace a sequential file instead of the target database stage?
Check if any other lock been held while you running the job.

For the category of Insert/Update, you need to do a lookup on the target to find whether the data is New or Update. So it can be a merely a lookup stage if the data can fit into memory or a join transformer, or CangeCapture stage. Based on the flag, you an insert or update the data in different stre...

There are several ways of doing it. Use Abort after n rows option available in Transformer. Or by counting the number of rows passing on a column, you can use AbortUlitility. Or Teminator stage in JobSequence(If you have in your version). You can search for this. But Why do you need to abort the job...

Reset and find more log in "From Previous Run..." .
But you need to say more about you job design.

I faced that issue in server edition 7.0 and not in 7.5 PX.