DSXchange

CLOSE_WAIT are waiting to close state. You can wait for certain more time till it dies by itself. Its interesting to see the operator level information in Unix.

Hi, You need to check the brchdm_file stage, to find the field which has been given as length 7, where as the actual file has the value as 9 in length. If you file is with correct metadata, you need to convert the length from 7 to 9. In the advance tab, the Preserve partiton would be by default as C...

Thats good to see that. According to document its both AT and CRON. Not sure where, what is been used.

So its certainly with the bind variable that you used in lookup. It could have been easily identified if you posted the query. Still I dont find it reasonable to populate a Hashed file and doing a lookup on Hashed file.
So do you mean the problem is resolved?? If so you can mark the thread as
such.

Could you mark the topic as resolved pls. Thanks.

Does you table have partition in Database?
What is the partition method used to partition data to 5 streams?
Could you explain the job design a bit more?

CRONTAB for unix.

No I am not checking for duplicate records. In my file anywhere I can have col2 value of previous record could be same as col1 value of current processing record. Ok, you need to compare Previous value of Col2 to current value of Col1 or the vice versa. User Transformer stage, User stage variables ...

Kumar, Can you please explain what is "CreateKeyChageColumn" Its the option available in Sort stage. Making this to True creates the column KeyChange. This column is set to 1 for the first row in each group where the value of the sort key changes. Subsequent records in the group have the column set...

If you are checking for Duplicate records and trying to divert to other file, use Sort stage to sort based on a column and assign "CreateKeyChageColumn". Using Transformer or Filter, divert the records whose values are 0s.
This has been discussed several times in forum.

It is the code for Load pending state. The previous run might have aborted with some error during load.
To get you table to normal form you need to run LOAD with the RESTART or TERMINATE option.

You need to give '=' after the parameters like /H /U /P.

SQL Builder has option called "Sort Order" selecting the corresponding column with sort method (Asc or Dsc) will give the required output, which doesn't require 'Where' clause.

High volume, more stages will always be a challenge to performance.
Is it all one to one, or joined together and later diversified.
If its one source to one target table, its better to have different jobs for many beneficial factors. You can run the jobs parallely as well.

But you said, its only with your machine and not with others, even for the same project in the same server???
Could you just confirm that. What if the same job been monitored from other machine?