DSXchange

When 6 fields are selected from oracle stage, the job finishes in less than 5 mins whereas the job takes around 30 mins to finish when 30 fields are selected. FYI - The time differential comes from the join and the amount of data it is throwing around, not any perceived 'performance issue' with the...

In response to your stats - Rows per second is a fairly meaningless metric. You're better off comparing bytes per second using the total actual bytes rather than the ARL.

Yes. At a very high level, more bytes = more time.

With no where clause? Nope.

(let me clarify here this col1 and col2 value will be same for that particular load) Should have clarified that right away. It's an important piece of information. and this variables were passed into sql queries whil loading the data. Can we do along the same lines using datastage. Of course, that'...

Good information on SyncProject.sh here.

And for something 'out of the box' you'd need to ensure the jobs abort rather than simply end with warnings if you want that to be the restart point. You could do that a couple of different ways, one would be to drop the warning limit down so that the first warning aborts the job. Another would be t...

Clear? Go back to whomever produced that specification and ask them how that is supposed to work. Without the join rules documented it is pretty much useless. All you know at this point is (I assume) what D & E records go in the table with a C record. But A & B? Who the heck knows? No-one on...

Suggest patience... it is a weekend, after all.

Let's start at the beginning. Do you have checkpoints enabled in the Sequence job? Do you understand that restartability is driven by aborts, not warnings?

Excellent. :D

The Pivot stage does require separate columns but Transformer Looping has no such requirement.

MT wrote:@MODERATOR: still missing the option for DataStage Release 9!

Not a Moderator issue.

That goes back to the site owner / maintainer.

Because they're not on a Windows server. The winexe software allows remote execution of Windows commands from 'UNIX'.

There are far too many variables to list here. Just wanted to note that this is a DB2 / database SQL issue and has nothing to do with DataStage. Yes, a database will typically cache query information so that if it is rerun in close order it could possibly go much faster the second time. However, tha...

OK... so you are dumping a portion of the file into the dynamic array that DSExecute returns and then looping through that. I can see that technique 'working' for small volumes but would never had put something like that together. You are probably hitting the upper limit of what that dynamic array c...