DSXchange

Set access method to Bulk, and bulk method to Update.

All this is documented in the Connectivity Guide for Teradata manual.

This should be available from the table definition you imported from the Oracle table.

All you need is the loop exit condition, a loop variable that extracts anything specific to that iteration, and transfers that to the output link along with any columns transferred with the input link.

Have you tried setting NLS mapping to "UTF-16 Little Endian" in DataStage?

Some developers seem to have the attitude that lack of documentation = job security.

Anyone working for me produces the design and documentation first, before being given the chance to play with DataStage (or whatever tool).

iq_etl wrote:We have removed columns not referenced, rows not needed, and use outer joins to reference the tables that have millions of rows.

The job no longer hangs up and takes only about a minute to execute.

You have been well advised.

There is no documented answer to that question. Presumably, from the behaviour you describe, dsrecords command uses the configuration file stored within the Data Set descriptor file (and, hopefully, throws a warning if any node is inaccessible at time of execution).

Run the ODBC Connector stage in Sequential mode. Set this property on the Advanced tab in stage properties.

Use Looping within a Transformer stage (assuming you have version 8.5 or later). Loop exit condition is

You can use the same technique in an after-job subroutine in a parallel job. From within a Transformer stage, however, you would need to have created a parallel routine (compiled, linked and recorded it) that you could call from the Transformer stage. That routine would use the DataStage API functio...

Which job is taking all the time? (You can determine this information from the job logs or from the Operations Console.) Why? (You can determine this information from the Performance Analysis tool in Designer.)

Better to initialise to "???" rather than @NULL - comparisons to @NULL always return @NULL.

Expose job parameters to receive these values. In the Job activity set the values for those parameters using the activity variables from the Exception Handler.

If a job doesn't have its own message handler it will use the project default message handler if one is defined.

If you enclose in Code tags, you will get a readable format.