DSXchange

Why do you claim that 300 rows/sec equals "poor performance"? Indeed, why do you believe that rows/sec is meaningful as a metric of ETL performance? It isn't, for a number of reasons. Look at all the elements of the path from your ETL job to the database including transmission over the network, conc...

I don't even bother to attempt to diagnose messages from APT_CombinedOperatorController.

Once you can establish which stage (operator) is throwing the error, then it may be obvious where it lies. Certainly we will be more willing to attempt to resolve it.

Search for "Character Set" possibly in combination with "DSX". That will reveal to you how "to resolve the issue" and is what you should have done in the first place.

Doesn't Search work for you?

This has been asked, and answered, in the past.

Have you read the pertinent chapter in the manual? Once you have done that, please ask more specific questions. We are not here to parrot the manuals.

Enclose it in Code tags and then make use of the fact that code is represented in fixed format font. For example: HashedFile | | V Source -------> Transformer -----> Target | | V SeqFile_Rejects Both reference input link order and output link execution order can be controlled from the Transformer st...

Welcome aboard. I suspect you are not using WebSphere Transformation Extender, which is the new name of DataStage TX, which has moved out of the sphere of "DataStage" products entirely. Therefore you can post your question in the correct forum, or wait till the moderator moves this thread there. Use...

You will find, if you examine the score, that DataStage has inserted tsort operators. To avoid these use explicit Sort stages with the Sort Mode property set to "Don't sort (already sorted)".

I need a Quick turn around from u guys.. We don't do "urgent". DSXchange is an all-volunteer forum whose members post as and when they can, if they have something to contribute. If you require speedy response sign up with your support provider for premium services, and learn the true cost of "urgen...

Please edit your post to enclose your job design in Code tags, then convert it into "ASCII art" to show us more exactly what connects with what. Use Preview until you get it right. It is not clear at the moment.

Are the Join stage inputs properly hash partitioned and sorted?

The Transform is entirely agnostic about whether or not the value on which it is operating is a primary key or not. If the argument is null, then 0 is output. If the argument is not null, then the argument is output. End of story.

Remove the index that you created with CREATE.INDEX.


Because you created the table with DataStage/SQL, you must also create the index with DataStage/SQL.

Check that you have the correct job selected when choosing Log view.