DSXchange

Thats completely DTS specific. Your better off getting in touch with DTS website. If you found that info from a reputable source online, then make sure you have all those patches applied.

Even though the hashed file is empty, you will not incur a fata error. What are the options that you have set while building the hashed file. Are you reading the same hashed file that you created ?

It will sort on column 'MGR' but other the rest of the columns are going to remain intact. Also, didnt get a clear picture of your second requirement.
Suggestion:
Get rid of the sort stage and put an order by MGR clause in the odbc stage. This way you will select sorted data.

Maybe something is happening at the database level. The database might not be available at that time. Is this the only job thats been acting up or you have other such jobs?

This post is a continuation of special characters. for those who might have missed it. NLS is a very powerful and complex feature. I have'nt used it myself but have learnt about it here. You may or may not need NLS enabled. Someone more experienced with NLS will throw some more light on it, as i don...

I think this is a good option. Gives an idea of what lies inside the post right from the forum index. Great thinking Roy

Dont provide @INROWNUM as the sequence name. Give a sensible name. Like maybe JobName. Why do you need the stage variable 'sv' again. If you dont, then get rid of it.

Ouch. I really hope that truncating the target was really what he wanted. Also, clear table and then insert will take a lot of time if target table is huge. You might want to re-consider this approach.

DataStage engine picks up the time from the server its sitting on. So if the server time works properly, so will your DataStage time. DTS is different in the way it works than DataStage. A patch might be required for DTS, but not necessarily for DataStage. As already pointed out, DataStage picks up ...

The derivation should be KeyMgtGetNextValue(SeqName) where SeqName is nothing but a name that identifies this particular sequence.

Do you have NLS enabled in DS?

The TNSNAMES.ORA file is either not there or is not updated with the current server that you are trying to access. It works with odbc because all that info is present in the uvodbc.config file and .odbc.ini file. Check and update your TNSNAMES.ORA file. Also, you can use odbc and DRS stage. Choose O...

The error message says it all. You need to handle nulls. Refer to this post.

File path changes will be a pain.
Welcome back Kenneth .

Are you building a fixed width file or a delimited file? make sure you have correct lengths for all those listed columns.