DSXchange

Welcome aboard. :D

ODBC drivers ship with DataStage. OCI client software is available with your Oracle software - contact your DBA.

Welcome aboard. :D Failed precompilation involves DataStage losing track of some kind of relationship between the objects in a job design. In Siva's case it was link properties; in your case it appears to have been either another link or stage properties. In any case you appear to have resolved it.

Use a UNIX find command to determine where SYBCTLIB is located. Make sure that its parent directory is included in your shared library search path.

What are you using as the value of the SMTP Mail server property?

Break the dates into their components (for example month_from_date, year_from_date in a Modify stage, or equivalent Transformer stage functions) and apply appropriate logic and arithmetic.

Where is SYBCTLIB ? Is this directory in your shared library search path (your LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH environment variable)?

The maximum number of dynamic (Type 30) hashed files that can be open simultaneously is controlled by the T30FILE configuration parameter (in the uvconfig file). This determines the number of slots in the in-memory table that is reported by smat -d command. Most of the Repository tables (DS_* and RT...

It's taught in the IBM Advanced DataStage class. Therefore it's documented in the training manual. I'm not aware that it's documented in any of the PDF manuals that ship with the product.

But it seems that the BASIC transformer will be unable to work on the parallel grid we are using. Who said? Of course it can - you just need to make sure it runs on a node where the DataStage run machine is installed. You can use a node pool or a one-node configuration file. for some reason they wa...

For a Lookup stage, "Auto" selects:

Round Robin for the stream input link

Entire for the reference input link(s)

The latter can have performance implications in a cluster/grid configuration, as all rows need to be moved to all nodes.

And Search doesn't work for you either?

Just curious - how are you setting the user status in a parallel job?

Your metadata should match. Failing that, you could include a TRIM or SUBSTRING function in the SQL statement.

Is tha partition table the same table as the one from which you are selecting? Is this truly a partitioned table?

What are you doing with the records downstream of the Change Capture stage? In particular, are any records loaded into the Teradata table (thereby to become a populated "before" data set)?