DSXchange

How? Honestly, after being here 2.5 years with 477 posts I'm a bit surprised you'd need to ask that. Unless you're not the original "karthi_gana" and have inherited the account?

Would be helpful to confirm (or deny) that so we can take that into account when answering...

I doubt anyone here can help, unless they happen to have seen and solved this same problem. In your shoes, I would get your official support provider involved.

As noted, you don't want to be searching "UV" but rather "DS_JOBOBJECTS".

Split to your own topic.

Move to the actual Server forum. Do your "header" and "footer" files contain a single row apiece? Or do you have multiple entries in each that need to be merged with the rows in the data file? For the former, the DOS copy command can do the trick for you: COPY HEADER+DATA+FOOTER ...

Yes... but why would you want to?

Why not filter them out before sending them to the target table?

I'm assuming you'd be OK going that route, maintaining the same hostname and IP address.

The link in Susanne's post shows a much simpler (and technically "more proper") solution.

At the moment, I don't see any other explaination for why it seemingly works for all group changes except from the first to the second.

And I don't believe you'll need to worry about the partition number, just partitioning things properly by the group keys should do the trick.

That could be a partitioning problem. If you are running on more than one node, a simple experiment should answer that question - run the job on a single node. Is the result correct then?

Just as a wee bit of a personal rant - anything using stage variables with names like "sv1" would never pass a peer review. Give them meaningful names, people!

That key change column is a boolean. When it is true (1) you are at the beginning of a new group and you should increment your "group id". While it is false (0) you should continue to use the current group id. Use stage variables to manage that.

Could you please tell me how to optimize the query below Typically by having a conversation with your DBA or Data Architect, people who have access / knowledge of the structures & volumetrics involved. All anyone could do here is give you generic advice about full table scans, hash joins v. nes...

Changing quotes won't make any difference. There must be something here we are missing (or at least I am), some vital piece of information left unspoken. Can you expand on your job design, specifically what "using nested condition to load table_a" and "not getting loaded" mean? I...