DSXchange

Does the Oracle DB match perfectly in terms of default date picture? (Clearly, from your example, it does not.) Therefore you either have to transform the string coming in from the sequential file so that it conforms to your Oracle default date picture, or use TO_DATE() function in your INSERT/UPDAT...

You might also reveal whether you have used the NullFieldValue property in your target Sequential File stage.

Sequential files don't have data types - they just have text. Try including a TO_DATE function in a user-defined SQL statement, specifying a date picture that corresponds with your actual data, that is 'YYYYMMDD'.

Follow the Member Benefits link from the DSXchange home page.

For a definitive statement go to the IBM Information Center for Information Server v8r7

I don't see anywhere in your SQL where you are using CAST to convert to Long VarChar2. Is this implicit in the CONVERT() function?

For a definitive statement go to the IBM Information Center for Information Server v8r7

VarChar should support 4000 in most implementations. Long VarChar should be able to support far more.

To achieve multiple instances you have to provide an invocation ID. This can be provided as a sequence parameter if necessary though, from memory, you have to type in the parameter reference - there's no "insert job parameter" control on this field.

Check the data type in the database table.
Check the data type in your job's metadata.

If you're using a Connector stage, change the "Fail on type mismatch" property from Yes to No.

Short of answering using all upper-case I don't know how any "higher level" might be achieved. Craig's answer seems singularly complete to me. DSXchange is not here to do your work for you (though some consultants who post here may do so for money). DSXchange will help, as Craig has done. ...

Use the 8dot3 name so that you don't have to have spaces in the pathname.

The command in your Execute Command activity has an exit status of 2 (which usually means "file not found"). View the sequence log to determine whether there was any additional output from the command.

As noted, you could use a server Folder stage, either in a server job or in a server Shared Container in a parallel job.

Or you could upgrade to version 9.1.2 (the latest), in which this functionality exists in the Sequential File stage.

You can't put the parameters in the Command field.
You can, however, put them in the Parameters field.

So, in your case, the Command field just contains COPY and the Parameters field contains the (parameterized) remainder of the command.

The compiler is needed to compile any parallel job with a Transformer in it. This has nothing at all to do with Balanced Optimization. I don't know whether pushing any of the job's logic into a database can be done without the compiler (my installations have always had it). It would surely depend on...

Split the job into two streams based on the date rule, run the data through SCD stage with properties appropriately set on each stream.