DSXchange

Do an exact search for "OMD.XML.DIR" here.

ylai20 wrote:I have try to use this method but it required input and output which i think is not necessary.

It's necessary. And since we're talking Server job, that dummy input would need to come from a Transformer. Make sure you define a stage variable in it and use a constraint of @OUTROWNUM=1.

Why not just append the needed number of zeroes to the string?

Craig/Ray, Here are the results of few runs Run 1: Followed Craig's tip. Removed IPC stages from the job, unchecked Enable Row Buffer and ran the job. Result: Same as old run. 1 row/sec from source link. On the reference links ~2000 rows/sec. That "tip" was only meant to be a starting poi...

Abhi700 - You seem to have missed my point... and still haven't clarified your source - flat file? Database table? Something else entirely?

If this "len(stripwhitespaces(col_name))=0 or isnull(col_name)" only rejects spaces then you don't have any nulls. What is your source?

Make sure that property is also off in the job itself.

Change the design. And I'm not suggestion reading directly from the database, I'm suggesting you let the XML Input stage read them. I'm assuming your job starts with a Sequential File stage that feeds the XML Input. If that's true, then you need to replace the Sequential File stage with a Folder sta...

The mismatch of speeds is an artifact of having buffering turned on. Honestly, in your shoes I would turn it off and then work through all of the normal steps of identifying the bottleneck(s) in the flow. Start by isolating the source and then working your way to the target.

They are all valid strings, in spite of your (I believe incorrect) date syntax. I would think you'll need to approach this differently: length = 10, count of "/" = 2, one at position 3 and the other at position 6. Or just the length check if you are certain they are always valid dates othe...

i was assuming jobs will abort after 50 warnings when we have "abort after 50 warning" option is set in director. Only if you start the job from the Director, hence my question. The Designer has a different setting which defaults to zero and which you need to change each run by switiching...

Sounds like you weren't switched back to the 8.1 client when you uninstalled 7.5. I assume at this point a reinstall of the 8.1 client is in order.

In order to get help from the largest pool of people, you really should restate the question in words - meaning, explain what the Oracle sql is doing. Or is that part of the issue?

Like I said, not a magic bullet. First order of business is to determine the bottleneck and see what (if any) tuning you can do, not just throw IPC stages at it.

10 hours with no CPU activity I'd lay squarely at the feet of the database.

Wabbit?