DSXchange

It means that the value does not match the metadata.

Nodes are dynamically allocated by the grid management software. The parallel execution configuration file for DataStage is dynamic, making reference only to generic nodes.

It's not only OK, it's mandatory. But DataStage thinks there's a zero or empty precision in there somewhere. Enable the environment variable that dumps schemas (from memory it's something like OSH_PRINT_SCHEMAS) to get a more detailed diagnosis.

Compare them against the link types you see in Monitor. Link types can include stream input, reference input, reject and stream output.

And when you reset the job after it aborted, was there a "from previous run" event logged? If so, what was in it?

There is no more detail, unless you require someone here to copy the steps (for creating a project) from the Administration guide into a post.

And that's not going to happen.

Maybe, maybe not. For 0 rows, definitely not. Times are only reported in whole seconds, so there may be no measurable difference for a moderate number of rows either. How many will depend upon how wide the rows are; you did not offer that information.

Go to the link ordering tab in the Match stage.

D'you mean that it's clever enough to recognize that you're English?!!

What's in the startup script (.profile, .bash_profile, etc.) for dsadm? For root? For jmckeever?

bicap wrote:Hope this helps..

Hope?!

Did you verify it?

If "Generate SQL" property value is "No" then you provide a compliant (one that matches the information on the Columns tab) SELECT statement in the "SELECT Statement" property. If "Generate SQL" property value is "Yes" then you provide the table name...

Assuming ANSI standard SQL, double-quotes indicates an identifier while single-quotes indicates a constant value. So check your settings (perhaps on the ODBC driver or database client connection) to ensure that ANSI standard SQL is being used. You might also try qualifying the column name with a tab...

(2) and (3) are identical, assuming the Force option is not used in the Copy stage. Adding a Transformer stage, even one that transfers data only, will add a small demand for resources.

... then there's no way the SP could SELECT rows, is there?

Why re-invent the wheel? Your putative routine does precisely what the Index() function accomplishes.

To the OP, you could also use grep as a Filter Command in the Sequential File stage or in an External Source stage.