DSXchange

Teradata does not have NVL() function, as discussed here - Teradata does have COALESCE() function.

Information about the services tier is to be found in the ASB node agent configuration information, which is at /opt/IBM/InformationServer/ASBNode/conf (assuming you've used the default installation location for Information Server engine tier). Inspect /opt/IBM/InformationServer/ASBNode/conf/agent.p...

Reviewing the response file for installation or the installation log would be my favourite.

The short answer is mismatched metadata between the two jobs. The longer answer requires that you identify that you are using the same key columns (in the same order), and that the location (position in the physical record) of each field is the same in both jobs. Fields are specified by location rat...

Run a job that has ExecSH as its before-job subroutine and execute the id command. The user that runs the job will appear in the job log.

You can (should) also use web console for Information Server to check the Engine credentials.

Since the entry shows "Multi Instance Job: N" I'd assert that you do not even have a multi-instance job. Checking the box is not enough - you have to re-compile in order for the change (from not multi-instance to multi-instance) to take effect.

Welcome aboard.

It is certainly feasible. But it will be easier to explain with an example. If we can use your example, as Craig suggests, then it will be easier still.

Download ETLstats (for free) from Kim Duke's website - much of what you want is there and you can adapt it, since source code is included.

For your second option consider a generic shared container.

TYPE and FIELD NUMBER and FIELD DEFINITION relate to how data are stored, which Arnd as covered. FIELD NUMBER relates to data fields while FIELD DEFINITION relates to computed fields. The remainder relate to how data are displayed when a query is executed; the default conversion (for example date co...

Use a server Sequential File stage in a server Shared Container and make use of its excellent missing columns functionality.

Or, if it's a small to medium sized file, use a server job entirely.

Use the Metadata Asset Manager utility and specify the bridge for "Sybase PowerDesigner PDM 7.5 to 15". (There is also a bridge for "Sybase PowerDesigner PDM 6.1" if you happen to have that version.) If you don't have Metadata Asset Manager, use Import Export Manager with the sam...

What does "best" mean in your context?

The CSV file was created in Windows. Change the Record Delimiter property to Record Delimiter String and set its value to "DOS Style".

In version 7.x the only table that contains information about previous runs - unless you preserve it in your own tables - is the log for the job, RT_LOGnnn where nnn is the job number.

I warned you of this in my post but, since you don't have premium membership, you would not have read that part.