DSXchange

Presumably you have some QualityStage stages in the job. But we can not help you, because you have allowed operator combination to occur, which has hidden the true source of the error. Disable operator combination, try again, and post the exact error message. Moderator: please move this to the Quali...

What do you wish to use for your test results database? Set up a system or file DSN to point to it, and supply that DSN and the user ID and password for that database.

Then make sure that the user ID has sufficient privilege to create objects (particularly tables) in that database.

What you are asserting is that you're not interested in probabilistic matching - you're only interested in creating sets of records in which all the blocking fields exactly match. For that's what blocking fields do.

Answer my question please. Which fields are being used for blocking and which (if any) for matching?

Replies to private email count as paid consulting. How do you want to pay? Have you visited the member portal yet?

Please disable operator combination and report the complete error message after running again.

There are environment variables that need to be set for Oracle, including ORACLE_HOME. Consult your Oracle documentation.

This is Itanium, isn't it? Check your shared library search path environment variable.

... and there are tools within Information Server/DataStage including the Resource Estimator.

will give a fairly good idea. There's also a hidden file (either in the root directory or in the DataStage Engine directory) that specifies who the installing administrator is. But I can't check this at the moment.

Or install dsjob and its libraries on the remote machine, and specify the DataStage server in the command line arguments.

So you have a number of blocking columns (which must match absolutely) and no matching columns. Is this right?

No, provided that you have set up other users with appropriate Information Analyzer credentials in Information Server.

Oracle typically requires parameter markers of the form :1, :2, :3, and so on, not ?, ?, ?. Or are you using ODBC?

Do not supply a value for the key column in your job design if you are using a reference to the sequence's NEXTVAL property in user-defined SQL.

This could be anything, even MicroFocus COBOL on Windows. We need to await Nicole's confirmation.