DSXchange

I've been working on actual development for a change. Here's an idea that can save one mouse click for every stage opened. When a stage is opened, focus should automatically be set to the first mandatory property's field value field. (Probably much more difficult to implement than to say but, hey, i...

"Schema" here does not mean the database schema in which the table resides - it means the record structure. (There are historical reasons for this, with which I won't bore you.) I would suggest that one of the columns (or more than one) is defined differently in your pre-production environ...

When you submit the run request from a client, visit the Limits tab on the Job Run Options dialog. When you submit using the command line interface dsjob, specify the -warn option. It is also possible to change the default globally, using Tools > Options (Limits tab) in Director. Note that this chan...

You probably need to mention the default value along with the nullable property in your schema file.

Aggregator stage, Non-missing values count output column calculation method. Split your data into five streams, one for each column to be counted. Eliminate all unneeded data.

The other best practice around operator combination is to disable it when the optimizer has become too greedy, and packed too many operators into a single combined operator (it will unthinkingly combine as many as possible that meet the criteria*), such that total demand for that process's resources...

Add Stuart's response to your Favorites.

Yes. Use $APT_DISABLE_COMBINATION as a job parameter (environment variable).

asorrell wrote:One big difference - you can't write NULL values to a sequential file. If the records contained NULL's they'd all bounce. They have to be handled explicitly prior to writing them to sequential files.

... or within the Sequential File Stage using Null Field Value properties, for example.

I answered the question "Is there any tricks out there to get the true DB2 error codes to go to the log?" I don't know any other "tricks" to achieve this result. I prefer to prevent error codes. Once you've figured out what the errors are you can fix the cause(s), then revert you...

ODBC Connector uses ODBC protocols, and needs to load an ODBC driver (maybe) which makes calls via the Oracle OCI. The Oracle Connector invokes the Oracle OCI functions directly. ODBC also has to translate between its "standard" data types and Oracle idiosyncratic data types. On these base...

Try setting Array Size and Transaction Size to 1, at least while troubleshooting. Like every other property in Connector stage types, these can be made job parameters.

Show us the error message(s) associated with the abort. Also show us the settings in the DB2 Connector for the rejects link. In particular, what kinds of rejects are you capturing and which kinds are you ignoring?

Check that RCP is enabled on the output link from the Transformer stage.

This is not the same as the stage properties setting - the Transformer supports multiple output links - the stage property asserts the setting for newly-added output links.

Try it with this job design.

Source (Dataset) --> CopyStage

Assert the Force property in the Copy stage.

I think you'll find that the Data Set is not the culprit here.