DSXchange

Yes, the imported metadata have to be stored in "the usual place" for IA; it does not just link to the original system tables.

Good luck getting the null in the final row!

We can probably do you a good deal on DB2

Seriously, though, you have to make the data acceptable to Oracle. Whatever that takes.

Sort key field not found usually indicates an issue with the metadata rather than with the partitioning.

Check every link thoroughly to make sure that the sort key column is present on that link.

Do a lookup against the primary key of the target table.

If that's too big, first extract a single column table made up of those primary keys and do a lookup against that.

But it shouldn't be necessary to do that, because the lookup against the primary key should be resolved in its index.

You risk a self-deadlock.

Click on the appropriate part of the picture in the top left hand corner of the Connector stage editor. This will select either the stage properties or one of the link properties, which will be highlighted in yellow. Once you've done that, the properties grid applies to that stage/link.

Good catch. Version 7.x supports whatever the operating system is using. So, if the operating system security is implemented via LDAP, then so is DataStage's.

-128 is the value with which you replace any null.

This can be represented as a single byte 10000000 (binary) which is also the DataStage internal representation of null.

You need a separate handle_null() specification for each column.

It is not possible to install DataStage 7.5 on Windows 7.

Have you set up Engine credentials using web console for Information Server? DataStage requires that each user have Engine credentials mapping to an operating system user (unless the operating system also uses LDAP in which case you can select "shared" credentials).

Take some training, from an organization like PR3 or IBM. Do an internet search for "DataStage training" to find other providers, but we cannot - for obvious reasons, recommend any one over another.

Or use dsjob command, which itself uses the API.

There may be other contacts on the commercial site http://www.dsxchange.net

You need to keep track of the rows that have been committed, and/or query the target table at the beginning of your restart run, ideally with every row identified with the run number that most recently changed the row. If you're deleting rows, even more tracking (keeping before-image) will be necess...