DSXchange

The complete logic is documented in the Information Analyzer User Guide.

For example, your two numbers are Int64 because they contain only numeric digits and a sign, and are too large to be Int32.

Don't worry about what's in the state file. Just use the Surrogate Key generator stage. It knows what's in the state file and how to use and maintain it.

You still have not answered the question about what version of the Update Installer you are trying to use.

That is correct behaviour. Anything with an aggregate weight below zero is necessarily a non-match, since the sum of magnitudes of disagreement weights is greater than the sum of magnitudes of agreement weights.

What did you do with the Format specifications?

DataStage always puts the zeroes in for Decimal data type, to prove that precision and scale are handled properly. You can only get rid of the zeroes if you use VarChar as the data type.

My guess: file has DOS-style line terminators but your job design format specifies UNIX-style.

... and maybe you are using a different version, and maybe you are running on a different platform.

When you start your own thread we'll have a better idea about your problem.

Is the final line in the file complete?

How do you handle the arbitratry number of values?

Possibly the last line is missing its line terminator character.

Once upon a time there was a multi-value database called GIRLS. Later other vendors jumped on the bandwagon but had different ideas about identifiers. One group (let's call them the Pick group) preferred the hyphen as a delimiter while others (let's call them the Prime INFORMATION group) preferred t...

It may be that you have an ODBC driver for Excel, even though Excel itself is not installed. In that case you can use an ODBC stage.

Use whichever one does not throw a metadata mismatch warning.

Some database products use "Decimal", others use "Numeric", some allow either.

Ah. Something akin to