DSXchange

Look in the server logs to find out why.
\IBM\WebSphere\AppServer\profiles\default\logs\server1\*.log

To test, emplace a Routine activity downstream of the Exception Handler, call DSLogInfo() and see whether the Exception Handler is actually firing.

Wouldn't it make more sense to execute as a user who does have the requisite database privileges?

Yes, but you have to wait to the end anyway to get the correct count.

The value of system variable @OUTROWNUM will be correct in the final row. Indeed it will be correct at all times on all output links.

DataStage 8.5 certification exam is now available.

Perhaps you can use Remove Duplicates stage rather than Aggregator.

You don't appear to have used the -fix option.

Take a backup of VOC then try to repair it. Log in as dsadm or root. If the VOC file can not be fixed by this method, delete the entire account and restore a good copy from system backup.

You do need a new DSN. It might have the same name as the old Informix one, but it will have a totally different definition, including the pathname of the library to be loaded and the port number through which to connect. Prototypes exist within the $ODBCINI file.

That one's easy. Don't send records to Oracle that violate that particular UNIQUE constraint.

You will not be able to get in to this project until the corruption is repaired. Unfortunately we have no information about which file it is. Based on the size and the message I'm going to guess that it's the VOC file. While attached to that directory, execute the following command to determine whet...

Is the data source name (DSN) you used in the ODBC stage correctly configured in $ODBCINI and registered in uvodbc.config file?

For starters, this can not be an unsigned value - it has a sign! Try changing the definition such that it is not recorded as unsigned.

For single-column integer keys Modulus is the most efficient key-based partitioning algorithm.

Can you delete the Data Set using the Data Set Management tool?