DSXchange

Are you extracting from two different Oracle instances as well, DEV and QA? If you are I'd think two things:

1) You are not using generated sql.
2) The default NLS_DATE format is different between the two instances.

In any case, switching to generated sql should solve the problem.

Oh, that dash. For some reason I was fixating on the leading dashes some lines have...

I was assuming the 'dash' was some sort of artifact of the cut-and-paste operation from whatever was used to view the XML and not actually in the file itself.

Sure looks like an XML Input stage could handle that for you as well.

...and then only if the view is 'updateable' I do believe. As previously noted, you could always target the base tables.

Actually, it looks like your target is a view. Load the base table(s) instead.

If 'keep the old value' means don't change it - set it to itself.

Bah, 1 million 12 byte records plus the overhead is a nit and nowhere near 2GB - as you noted. You'll be fine with a hashed file solution - from a storage standpoint at least. Ray has posted the gory details and all the overhead you need to include to get an accurate size estimate more than once. Wh...

Interesting calculation. More to it than that, but regardless - try it. Let us know.

...and if you are using hashed files that may exceed the 2GB boundary, make them 64BIT hashed files.

That can't be the complete code. Also curious what your VB script you are calling does.

I don't see how that would help. The OP stated that it failed occassionally, not constantly. Lack of that JOBCONTROL header file would cause something that needed it to not even run.

Haven't seen that one. Post details of your job design, specifically the properties used in the Start Loop.

That's a database constraint, not a DataStage one. Probably best to talk to your DBA and see what your options are. For example, if you have the grants you need you may be able to disable the FK constraint in the 'before sql' tab, do the truncate and then re-enable it 'after sql'. Other places setup...

Well... you would do that to pass data between jobs. Usually, to pass something between stages, all you need to do is add that new field to the link between the two stages. Why make this more difficult than it needs to be? The other option is 'COMMON' storage. Or one of those five available @USERn v...