DSXchange

Then I have to assume you are doing something wrong here. Since we can't see what you are doing, all we can do is point you in the general direction but the solution is in your hands. Double-check those other jobs for clues to see what you might have missed in this one.

Not having installed with NLS doesn't mean there's zero support for it and the $NLS_LANG you use in your job is still important. Is that not set at all in the job's environment?

Both.

I would suggest going the DS.TOOLS route from the command line, not any client tool. And do so immediately after rebooting / restarting to ensure there are zero left-over processes running. All it takes is one to make the whole exercise a waste of time.

Figured it was Teradata something-or-other but my Google-Fu was failing me.

Second log message of any job will have a complete dump of all environment variables in effect when the job ran.

Did you have any disk space issues recently on the disk / partition where DataStage is installed? Version 8 adds more places for things to go wrong, but perhaps a good old fashioned rebuild of the project indexes will still help. Do an exact search here for DS.REINDEX and see if it fixes things for ...

Unicode is a whole 'nother kettle of fish. CLOB is CLOB or LOB or BLOB or LONG in Oracle and the metadata would come in as LongVarchar. How did you import the metadata, through which utility? If it wasn't the Orchestrate based one, try that one and use the metadata it creates. 11g isn't officially s...

How many nodes? I would assume some kind of issue with your hash partitioning, in spite of the fact that you seem to have that covered.

TPT? I can't find an acronym online that makes sense for a plugin and I'm guessing it don't mean Trailer Park Trash as Urban Dictionary would have me believe.

Meaning, they don't show up in the Repository Browser on the LHS of your screen? Do other jobs show there, just not these newly created ones? Is anyone else having this problem or is it just you? Leaning towards some kind of permissions issue but would like to hear your answers before we go too much...

Then it's not in the right environment, the one the job uses when it runs. Set it in dsenv instead. That or explicitly set the vaule in the Project to what you need it to be (this rather than $ENV) but still stick with $PROJDEF in the job.

:!: Not in this forum, which is for questions or issues with the site itself or a particular forum. Since yours is obviously a PX question, it needs to be reposted in the Enterprise Edition forum. Before you do, however, try doing an exact search of the site for "Converting a nullable source to...

Please answer both of my questions. Are you using any constraints on your (non-reject) output links? Rows will 'reject' if they go down no other link or if there is a 'write failure'.

Any particular messages being logged by the job? How exactly are you doing your null handling?