DSXchange

No, because operator combination is preventing us from determining the operator that is actually generating the message. I suspect that you have a substring function, in a Modify or a Transformer stage, in which one of the numeric arguments is being supplied with a non-numeric value. But it is not p...

Welcome aboard.

DataStage documentation is specific: BLOB is not supported.

What is the data type of your stored procedure argument? If it's not a string, then the quote characters may be causing the error. You also need to investigate the CREATE EXTERNAL TABLE statement within the stored procedure, since it is this that is throwing the error.

Experiment. Change the write method to Load and investigate the available properties to add under each of the properties folders. You can thus answer your own question. You could even refer to the Chapter in the Parallel Job Developer's Guide that discusses the Oracle Enterprise stage.

Mayur Dongaonkar wrote:We want to keep it between single Unix shell script and multiple Datastage jobs in it.

Then you're on your own. DataStage provides a tool: you choose not to use it.

That is not the error. That part of the message shows the location of the source code that is being compiled and the object code that is being generated. Please post the remainder of the error message.

Killing the SORT stage while it still had heap files on the scratch disk was probably the cause.

Try using sort as a Filter command in the Sequential File stage; the Sort stage is substantially slower than the UNIX sort command.

How many input rows are there? Create a second output from your Filter or Transformer stage that handles the logical inverse expression (or use an Otherwise/Log output link). Let us know what the row counts are. If you are in a Transformer stage, use the expression editor to build the expression; th...

Check the "log warning" compilation option in your job sequence's properties. Look in the log of the job for which the warning is generated.

Or switch to Status view and find it there by inspection.

mcs_suresh wrote:Row generator doesn't allow the integer datatype. It accepts only the varchar.

Please explain why you believe this to be the case.
I use integers a lot in Row Generator stages.

Each row selected is processed separately by DataStage. The only way you can create a loop is in a routine. But do you really need to? Is not the loop based upon the rows you are processing? In that case, all you need to do is to initialize and derive an appropriate set of stage variables in a Trans...

Mathematically 8/16 is 0.5, so maybe you're running on a machine with only half a CPU.


Or maybe it just seems that way.

You don't. But in your original post you did not mention that you had created the environment variables in the new project. Please post the exact message being logged when the jobs abort in the new project. Also check (in the "job starting..." event in the job log) that the job parameter values are ...

If you hard code the initial value as 0 and the increment as 15 then each of your processing nodes (mentioned in the configuration files) will have the same sequence generated, namely 0,15,30,45,... This is probably not what you want. If you set the initial value to PART and the increment to PARTCOU...