DSXchange

Data Set can happily store NULL, so you don't need to substitute anything else. This substitution technique is only relevant to sequential files and File Sets.

Sessions per Player is a property in the Teradata Enterprise stage, which is what prompted the original question. You need a bit of understanding about how DataStage interacts with Teradata to really get a handle on the best settings for these properties; you are trying to get as many sessions out o...

Both syntaxes are correct (Shane's is called "delimited substring extraction") and will generate exactly the same object code.

It's true that there is no Version Control with version 8.0. But I feel that reverting to using packages of released jobs would be a big step backwards. The future (version 8.2?) holds an interface to "traditional" source code control products, such as ClearCase. In the meantime, how about using DSX...

Job properties window has a "Generated OSH" tab. It should be there. If not, you need to enable Generated OSH in Administrator (project properties, Parallel tab).

Is this job using a Teradata Enterprise stage? In any case, the message is clear. Your configuration file has four nodes, but your job is so simple that it generates only two player processes. Therefore two of the nodes will remain unused. Maybe you are running stages in sequential mode rather than ...

Partly. It's why best practice is always to set up $APT_CONFIG_FILE as a job parameter so that you can run a job using different configuration files, depending (for example) on the volume of data to be processed. For example, a retail DW might ordinarily use ten nodes, but during the post-Xmas sales...

Or from your friend, perhaps.

Visit DSXchange home page to learn its coverage. There should be no reason to expect help on ERwin, Zen, motorcyle maintenance, or any other topic from this site.

To get rid of the message, avoid inserting rows for which key value already exists. To do that, perform a lookup against (an image of the key values from) the target table.

THere is, theoretically at least, an infinite amount of knowledge in the universe, therefore it is impossible to get it all. Infinity is unattainable.

"Turned off" by creating job parameters with these environment variables and setting the default value to $UNSET.

Need to give some thought to the other questions...

"Optimized" varies on a job by job basis, and indeed even on a run by run basis. There is no such thing as a "one size fits all" configuration file.

Can you please post the job design and generated OSH? Somewhere there is a file unit not being allocated. This may be because of a missing property, or that you have hit a limit on your system.

The disk cache tunables are only for hashed files, and therefore are irrelevant in the context of parallel jobs.

The mindset that you need is that DataStage is just another client as far as Oracle is concerned. So the usual environment variables, such as ORACLE_HOME, need to be set up for DataStage (in the dsenv script), the DSN (for ODBC) is set up in .odbc.ini and in uvodbc.config, and Oracle client software...