DSXchange

What is the Oracle definition for this column?

Either the CPU or the I/O will be high while this job is running. If the CPU is high then your bottleneck is parsing the input string, if the I/O is high then you are limited by that factor. If neither is high then you are being limited by some other factor.

Writing 3 column values of "x" "y,y," and "z" in a pipe delimited file with double quotes results in:
When you read this using pipe delimiters and double-quotes for strings you will get exactly the same results.

I don't see a bug or a problem here.

Rounding "10690164.245" to 2 decimal places gives "10690164.25" using nearest value.

You could force matters by doing a trunc_zero after adding 0.005 to positive numbers or subtracting 0.005 from negative ones.

What is the ODBC Data type for this column declared as?

Please explain exactly what format you are writing to the file in your server job portion. Is it a standard CSV type file? When you replace nulls to '' (string of length 0) then you should not be getting an rejects upon reading the sequential file PX. Please post a sample data line and the exact PX ...

Since your problem lies in having embedded commas, you need to ensure that your strings are quoted when writing to the sequential file. CSV files do not need to have commas as separators, quite of semicolons are used and theoretically any separator could be used. what did you specify as your separat...

If you look into the Connectivity Guide for Microsoft SQL Server and OLE DB Data you will see that all string types get mapped to DBTYPE_WSTR which should handle big strings. Simplify your problem by removing Oracle ODBC and replacing that stage with a PEEK stage. If the error remains, see if specif...

Although you can test it for yourself in a couple of minutes, the answer is that you can do string comparisons, e.g. "2010-01-23" < "2010-01-26". In your case the format is YYYYMMDD so a greater/less than comparison will work.

In the sequential file "Format" tab, select Field defaults -> Delimiter to be a value other than the default "comma".

...I checked with DS admin for I/O process during that time and it was quite minimal it seems and so the CPU usage. Something isn't correct here - either your CPU or your I/O Bandwidth is going to max out in this case. Could your disk be on a SAN and thus heavy disk use might show up in the form of...

What is your CPU usage during the job run? At the moment you don't know if I/O, I/O per process, or CPU Usage is the bottleneck.

To be more specific, "FIELD(In.Column,"-",1)" is the name, "FIELD(In.Column,"-",2) is the user-id.

Do you also have "Read from multiple Nodes" turned on?

I would try turning on "Read from multiple Nodes".