DSXchange

No. Just like a sequential file you just read them, then perhaps filter from there. Or load them into a database table, then query them to your heart's content.

You don't "query" flat files, you read them. After that, you use whatever stage is appropriate for the "transformation", the original source doesn't matter at that point. If you still need help, try explaining what exactly it is you need to do - without using the word "query...

What are you getting?

Sequence job. Seriously.

Several of the included routines use COMMON, and many are in the 'RowProc' group if I recall correctly. Look at their code as well for example usage.

Right, has nothing to do with DataStage directly. Best to just google for it, for example here is a Linux version but the instructions are fairly generic.

What makes you think it is 'picking up c4 instead of c3'? Are you using the exact same metadata in the lookup hashed file as the hashed file was created with?

ps. You should have done a CLEAR.FILE on your log file name as noted in the error, not the completely unrelated "phantom" directory.

while running the job for custom query with update and insert login on target table This confusing statement was why I thought you were using custom sql on the target. :? Best way to 'avoid' these kind of issues is by pre-qualifying your actions using a reference hashed lookup and two dedicated tar...

It will go into the target intact unless you explicitly remove them. How are you certain that they are gone before you send them to Teradata? Have you added a logging link (or three) to check?

I meant the "update and insert" dml not the source query, I thought that was your "custom" one. And your phantom is strictly from blowing the logs over 2GB in size just as it states, probably by running with unlimited warnings allowed.

I would suspect it's an issue with your 'custom query', that and loading multiple records with the same keys in a run. Why custom rather than generated? Care to post it?

Just wanted to pop back in and tell Sreeni I really didn't mean to single them out or anything, it's just that that is one of my pet peeves and I guess I was feeling a little... peevey... this morning.

Well... first thing would be a better idea of what "not working" means - error? warnings? odd results? Specific examples would probably be helpful as well.

What is "sysDate", something custom? Are you certain that exists in your other environments?

Not sure what link or file you're talking about here.

I took a different tack and searched for the "nPartition" part of your message, you might try the same but first see if this post fixes your problem:

viewtopic.php?t=122429