DSXchange

How many nodes does the job use? Assuming the 'partition 1' problem is a DataStage issue rather than a Teradata issue, perhaps running on a single node would solve this? Or running the stage in sequential mode, if applicable? Or using 'Entire' for the lookup partitioning methodology? :? Guessing here.

Interesting... don't recall ever having seen a project indices problem present itself with symptoms like that.

Marking this topic as Resolved for you.

The 'M' didn't work how? Making something 'multi-value' has absolutely nothing to do with a multi-row result set, by the way, so I guess that makes my question rhetorical. As noted in many other posts here, you would need to build the hashed file with X fields as the "key" and then use &qu...

So... is the job actually still running? Can you find processes for it when you grep? Either you have a locking issue (if yes) or (if no) a need to clear the status file from the Director, it seems to me.

Come over to the dark side, we have cookies! :D

Yah, there's no magic, you are in full control of that. And you'd probably want to add "hours" in seconds as in 3600 seconds at a time.

... that or someone can push the button for them. <click>

Why? Probably because it's new and different and smells funny.

I haven't been through this personally, but I assume the "do not select metadata repository" warning for the install is because that means you want to use DB2 for that and it will (attempt to) install and configure one for you if you do. So it doesn't surprise me that you would need to pre...

I'd also look for any differences in the log message that dumps all environment variables in play for any given run, any key value differences between standalone and sequence?

No.

Then you should probably involve your official support provider, perhaps there's a fixpack or patch you are missing.

Sure, simply override the Oracle specific environment variables in those jobs - things like ORACLE_HOME, LD_LIBRARY_PATH, etc. You could do that by adding them as user-defined variables in the project, where you could set their value to $ENV and then override their default values after bringing them...

All of which comes from the metadata repository... there really isn't anywhere else to 'export' from in DataStage. And the 'import' goes right back into the repository, regardless of what makes it up.

Not sure how many times you want an answer to this... and the answer hasn't changed from the other two times.

Export from the old. Import into the new.