DSXchange

For v7,

Take export and do a diff.

Even though Ray's point is valid for updates, the significant difference in update performance compared to its Server counterpart indicates issue in the design. Check whether there are any duplicate keys in the data which is causing locks in the target update. Also check whether the target has paral...

Configuration file depends on your hardware. So different installations must have different configuration.

Download both results in a sequential file and do a diff.

Check whether there are null values in non-nullable fields.

Gavin,

There is another similar post with information about the patch. Please search.

Why not use the notification activity ?

aka web console

Did you try an explain plan ?

How many of the total rows in the target will be updated in one run ?

You can achieve it in various ways.

One of them is via Matches as Craig has noted.

Sample

If the target is any dbms, you can set the values in the backend.

This can be done using a trigger.

You can create an 'on update' trigger which does

:new.col5 := :old.col5;
:new.col6 := :old.col6;

There are many other ways to handle this.

What is the source ?

What is the data volume ?

That appears to be the job of a reporting tool and not an ETL tool like datastage.

You can do that in Excel itself.

DB2 nodes or DataStage nodes?

You can achieve this in several ways, but all depends on how the load works. If you current load is direct into target, you can do this. But if it computes on the fly, you may have to work around that. If you can identify the last successful rows, you can add a 'id > targetID' in your source where c...

Your requirement appears bit unclear to me.

If that is what you expect, you can send the columns in 3 seperate link, sort and write to individual sequential files with record delimiter as blank for first 2.

In the after job stage you can cat them together.