DSXchange

There are lots of configurable limits. What stage types are you using? Have you examined tuning buffer sizes?

To answer your final question, can you do it in Teradata if DataStage is not involved, for example through BTEQ?

Disable operator combination so you can see whence the error is being generated.

I think mcs_ravishankar meant Lookup File Set but got confused.

Monitor view in Director

That's not the record schema. The record schema can be obtained from the generated OSH (in job properties, if enabled) or from the score.

You design what you need.

Server jobs are particular about metadata; with parallel jobs you can use the Schema File property to be a little more flexible, but you still need to map the various different target columns from source.

Surely there is a small and finite set of metadata variations?

Doing server-only stuff this week - someone else will need to reproduce the symptom. Your support provider, perchance?

Indeed, no. Some of the larger sites are even opting for a four-tier installation:

DataStage Clients

DataStage Server

WebSphere Application Server

Information Server

all on separate machines.

Bring $APT_STRING_PADCHAR into your job as a job parameter and set its value to " " (a space character).

This error occurred during View Data. Does your job actually run?

I would suspect that the index on DS_METADATA has become out of synch. This table probably needs to be re-indexed. Schedule some time when no DataStage client is using the project and re-index the Repository.

No, because you are not using an ODBC Enterprise stage.

Are you using the GUI (the expression editor) to create the expression? Sometimes typing in the name of a job parameter in an expression does not pick up the fact that it is tagged as the name of a job parameter. And, of course, mis-typing the job parameter name will always cause a compiler error!

Data Browser always shows leading zeroes for Decimal data types, to prove that the precision figure is being managed properly. Internally, decimal numbers are stored in binary format, so the leading zeroes are not really there - it's an artifact of View Data.