DSXchange

Perhaps someone used "kill -9"? Are the any DataStage processes left? If you start datastage you should see a "dsrpcd" started as well.

Yes, but you need to wait a bit of time between the stop and start and make sure that all processes have terminated.

It looks like process 1695892 might be hung. Do a "kill 1695892" and see if the defunct processes go away and if you can login to the client tools.

a) could you randomize that data a bit by editing your post and making the names and email addresses illegible?
b) did you cut off the last double quote by mistake?
c) which column is "AFFIL_EMAIL_CNTCT_IND"?

Your data is different in row 732966, I suggest you try

"head -732967 {SourceFile} | tail -3" to see one line before and one line after the incorrect one. The line length is short enough so that you should be able to detect the anomaly.

Those "defunct" processes shouldn't be there anymore. What does "ps -ef | grep 1695892" show? The PX jobs aren't using any system time, either. The processes show that you still have a couple of client tool sessions open on the system, though. If you still cannot login to any client tool it might be...

Your data and metadata need to match. You have rows which contain more data then your metadata allows for.

What is the output of "ps -ef | grep ds"?

I don't have any direct answers - but what about sending the decimal value to Teradata as a string and then doing the strnig-to-decimal conversion inside the database, would that work?

Do you have other projects on this installation and can you login to them?

It sounds like you have two problems - one is a long run for a job, and the other is no longer being able to login to DataStage from any client.

Is there still a process called "dsrpcd" running? If you do a "ps -ef | grep ds" could you post that output?

UniData is a different database; you won't be able to import those unless you have a UniData database system visible to your PC. I think you are lokoing for UniVerse hashed files.

Do not install NLS unless you know you need it. If you just need to read/write non-standard LATIN characters then that is not a reason to implement NLS. If you will need to do sub-string manipulations on multibyte data then you have a clear cause for implementing NLS.