DSXchange

Not sure about "pros and cons", whatever works is a pro in a manner of speaking. Me, I'd prefer the second approach as it makes what you are doing more obvious. I'd probably add an explicit Sort stage as well.

If we were talking about Server jobs then I'd say yes, definitely. However, I'd first try the APT variables that Eric posted for Parallel jobs. And you don't need to set them at the project level, you could start with just adding them to the job in question before you decide to set it project-wide.

Well, 15 is a magic number and (from what I recall) the default precision limit under the covers in DataStage. Problem is I don't recall and couldn't find via a search how to change that... guys, is there an APT variable for that? In uvconfig?

Changing the array size to 1 could 'solve' the problem but at the cost of it running very slowly, you'd have to wait for it to complete to know. And are you certain you managed to run it on a single node? If you had I don't see how it could have deadlocked with "another process" - assuming...

My understanding is an unbound Oracle NUMBER is stored in floating point. Still, not sure why that value would be truncated during RCP - perhaps there is an APT variable that needs to be set? Or perhaps a patch.

An unbound number with no precision like NUMBER rather than NUMBER(15)? Both sides?

Are you updating the same table you are selecting from? Does the job work without issue if you run it on one node?

So your source and target are tables? What database and what are the datatypes of the actual source and target database fields?

Thanks for starting a new post, that's what you needed to do rather than find an old 'similar' post to add your question to. And rather than doing both.

ps. I deleted your 'extra' copy of this.

So... you posted in the general forum with Job type noted as Server and additional info that says "8.5 parallel". Is this a Server or Parallel job?

It can take a few days as it's still (from what I understand) a manual process.

I have a specific request. Please start a new post when you have a question of your own, this rather then adding it to an old conversation you stumble across when searching. I've split you out to your own post and made up some details. Please let us know if you're not on version 8.x and a UNIX ETL s...

That's perfectly allowed, you just have to build the string "around" the parameters so they get a chance to be resolved before becoming part of the string:
Completely made up example but hopefully you get the idea.

So this is with just one particular job? Everything else works fine?

This job, did it stop working after it had been running fine or has it never run correctly yet?

mdbatra wrote:looks like I can view only those premium posts which were posted after I received the premium membership

Well, it's certainly not supposed to work like that and I don't recall every hearing that problem before. Odd.