DSXchange

Set it to whatever you like, it doesn't matter and is ignored for the process.

Remote shell.

You would need to leverage the UNIX 'dsjob' command, documented in the Server Job Developer's Guide in the Command Line Interface chapter. That or the API directly.

So, as noted, a mismatch. Remove the target column for the sequence from the stage.

An empty string "" is not the same as a null, well except in Oracle. So either check for both in your job or convert it in your source SQL. For example in Oracle:


Would do the trick.

Which has been asked and answered before. Search for "does not fulfill the sort requirements of the downstream operator".

If DateFromDaysSince is "not working", can you confirm that your CHANGE_DATE column is in fact a Date datatype and not a string?

Or just use the DateFromDaysSince function with a -2 for the number of days.

Field : CHAR(9)

kumar66 wrote:Fatal: ORA-01036: illegal variable name/number

You have a mismatch between the number of columns in the stage and the number of parameter markers in your SQL.

Based on what? Your clairvoyant knowledge of their naming standards?

You are overly complicating your solution, nothing you are doing here is magic nor requires a stored procedure to implement. m However, in an attempt to answer your question - the ODBC stage with custom sql is probably the only place where you can get away with no input parameters. Other stages typi...

In the ODBC stage itself - Inputs / General tab if you mean the 'Create table' option. Everything is normal DataStage design, not trying to explain anything... tricky.

No, because not all columns are bound in the query. Remove the 3 unneeded columns from the stage (1,2,7) and start numbering from :1.

The "order by" won't affect the actual lookup itself but can affect the hashed file population. Where exactly do you "order by"? And "rejected" in this case means the lookup fails?