DSXchange

Identification of them is the first step, after that you can work on ameliorating them. What's going on in the Java transformers? Any way to replace them with native DataStage functionality?

Of course. Which is why they are known as bottlenecks.

dongyingying wrote:try to find a way the sql run first and then columns not needed !

Posting the sql involved should help. Are you saying that you don't know the "columns not needed" because it does a select * rather than specifically naming the ones that are needed?

Sorry, but I have absolutely no idea what you are trying to ask or do.

Don't you think it would help to show us your SQL?

My requirement is to design a job which would create a table (teradata) by itself and should get loaded from the input file. Clarify your requirement, please. Do you need to create this table once (the first run only) or is it ok to drop and recreate it each run? The advice you are getting is for t...

You two need to learn to use the Reply to topic button rather than always quoting everything. I just had to go and clean up the mess this thread was, each reply getting bigger and bigger... sheesh.

Parens are an accounting mechanism to show negative numbers, so you'll find () around a negaive number rather than a minus sign. You'll need a mechanism to recognize that the parens are there and if found, remove them and then after converting the string to decimal, multiply the end result by -1. Ex...

Not sure... you could always ask your official support provider and let us know what you find out.

Am I incorrect in stating that the error message implies an attempt to import a fixed-width file? Or at least what the stage believes to be a fixed-width file? Reading a delimited file does not entail needing to know the exact byte count of the record, instead it reads to the end-of-record mark and ...

Which, it seems to me, is what the array size restriction would handle. Nothing in the upsert operation that I can think of - nor any of my personal experience with it across multiple tools - would require a transaction size of 1.

Interesting, that's the same "limitation" that Version Control had, from what I recall. You should be able to work around it using soft links...

They're not the thread starter, so they cannot. However, there seems to be enough information here, so.... <click>

I was wondering about that... I thought they ran 0 thru 6 rather than 1 thru 7. Would be interesting if the default changed somewhere in the 8.x release pipeline.

Why not share with us the error that you are seeing?