DSXchange

The problem with a bulk load versus PX is the coordinator node. In a partitioned database like DB2, you have a series of clustered servers (nodes) that each contain a portion of data for partitioned tables. ALL data has to go thru the coordinator node to decide where the data will reside. Using a bu...

You are fine to mix and match a series of server and parallel jobs. In fact, using PX jobs for extracting and loading to/from DB2/EEE has the advantage of directly accessing the method by which data is partitioned and bypasses the coordinator node for faster data access. If you have a separate job f...

What do you mean by "it stopped allowing other users to the system"?

Use the DS Manager client and do an import of table definitions using the Oracle Plugin.

Search the forum, this has been covered lots of times.

Stopping the job via Director will cause the job to abort, which means that the COMMIT at end of processing will NOT occur. As long as you have it set to 0, no rows should commit by using the STOP button in Director.

Hey wait a minute, I DON'T use the technique because the GUI represents this as invalid and Ascential could close the door on this technique at their perogative. I think the functionality SHOULD be there to do this (remove the half-hearted GUI attempts to block it, you can still type in the column d...

Yes, but whhhhyyyyyy is it frowned upon. Sometimes my priorities are considered "chicken-littleish".

Or, this undocumented functionality may be removed in a subsequent patch, minor, or major release without notification. Doing what you're doing is exploiting a non-enforced trap in the GUI, obviously the RED is meant to say you shouldn't be doing this. Were this functionality to change, you're jobs ...

Have you searched this forum? It's covered a lot and you have to be more clear about how you're needing to implement one (type 1, 2, 3, modified 1/2/3, etc)

Lots of ways: 1. Load each dataset into a separate table and use a join with one table as the driver. 2. Load each dataset into a separate table and use a UNION with a group-by with MIN/MAX operations on all columns mapping each table into a discrete set of columns. This gives you a full outer join ...

Although you have 10-12 hits against the same hash file for different rows, even potentially the same, the effort can be mitigated by using the shared hash caching check box under job properties. The memory footprint will be minimal, as they all share the same in-memory image of the file. Now, how c...

Search this forum after reading the manual. Here's a good discussion that may interest you: http://www.dsxchange.com/viewtopic.php?t=85364

Under job properties, performance tab. Try disabling inter process row buffering and don't use the project defaults in case it's turned on there.

As each release rolls out, some things work differently. One of them is the scaling factor on sequential files used to be irrelevant. If you perform some operation on a column DS re-applies the scaling factor to the data. So, you might want to verify that your data isn't getting messed with. We foun...