DSXchange

Another step is needed, because a DataStage project is also a schema. The command required is VERIFY.SQL projectname This should report that the directory does not exist, and that that's a fixable error. In this case, make sure you are logged in with DataStage DBA privilege and execute VERIFY.SQL pr...

You might also like to investigate the concept of rapidly changing dimensions, so that you have the complete picture.

We normally advocate four phases.

Extraction to first staging area.

Jobs presupposed by Transformation phase (e.g. loading lookups).

Transformation into second staging area.

Loading from staging area into target.

If you have 7.5 it will do the documentation for you (including the bitmap of the design). Find the tool in the toolbar that looks like it invokes Internet Explorer. A tool tip will appear if you hover the mouse pointer over it.

It may be that there are more tables needed. Check the SQL to create the tables, compare to existing database (or SQL file for 7.1 if you still have it).

DataStage has a "MetaStage proxy mode". When this is enabled, process metadata are collected automatically by a listener process and sent to the MetaStage hub. You will have all this explained during the training. MetaStage does not automatically capture database statistics (you need to do this with...

You don't get any mechanism for altering the job status apart from DSLogWarn and DSLogFatal, and setting the ErrorCode argument of a before/after subroutine to a value of other than 0. All of these except DSLogWarn cause the status to be 3; DSLogWarn causes the status to be 2 unless the job aborts f...

Hi Michael, DataStage is, as far as Oracle is concerned, just another client application. So all you have to do is to configure the DataStage "server" machine with whatever Oracle client software is required; that is, the ODBC driver for Oracle (one ships with DataStage) and the Oracle client softwa...

Check the file dsdlockd.config in the $DSHOME directory on the server. Is its auto-start set to 1? If so, check that there is a running process called dsdlockd It may also be that the aborted jobs are using large hashed file caches (I vaguely remember that your site sets the size to 999MB). These mu...

Just the obvious one. Reduce the load on the Oracle machine (perhaps by scheduling DataStage jobs better) or throw more hardware at it.

If it's the development environment, have developers test using a couple of hundred rows rather than a couple of million.

Best scenario, especially if you have lots of indexing on the Red Brick table, is to use the bulk load stage with automatic load disabled, then use the parallel bulk loader (rb_ptmu) from an after-stage or after-job subroutine. This allows separate processes to load the table and the indexes, in par...

Assuming that you're using 0 rows per transaction, much the same kind of explanation. You send all the rows, but hold off sending a "commit" until the end. It's not until that point that Red Brick can start actually loading rows into tables and updating indices. Your DataStage job waits for the "all...

True... unless... did the job fail to complete successfully and the "run after-job subroutine only if job completes successfully" check box was checked?

There's other stuff in dsd_gci.h that needs a licence. Try creating your own header file just incorporating the relevant prototype. Apart from that, it's not something I've done, so I await the results of your experiment; any additional advice will be purely theoretical. Has your support provider su...

The parallel job's Lookup stage allows for conditional lookup, and supports a business rule for handling the situation that the condition is not met, separately from the situation that the lookup failed. This is functionality that would be really useful in server jobs but, sadly, isn't there. Phil W...