DSXchange

Just curious if you have run the procedure outside of DataStage first and know for a fact that it indeed works as desired? Trying to debug something like this from inside a job can lead to madness, which is why our first rule is to always makes sure it is working on its own before roping it into a j...

True... and when it forces the array size to 1 it will note it in the job's log from what I recall.

I don't think you have any choice other than the 'padding option', i.e. put the leading zeroes back on after they get stripped from the fields where they are significant. To (mis)quote an elder statesman of science fiction, The Excel is a Harsh Mistress and you generally need to work around what it ...

I would make sure your Array Size is set to 1, if you haven't done that already.

Probably didn't really "work work" as "2014-01-01" isn't a date but rather a string. So what you posted as working would be fine if the actual target data type is a DATE (which is why you only would need the format for the input string) or the original post would be close to what...

This might help.

Thanks Uncle Ken, wherever you are!

Define what you mean by 'generic' here, please.

Pretty standard way to handle 'strings with spaces in them'.

Welcome. That's... an interesting list. For grins, can you verify we're talking about a Type 2 dimension here?

ps. Not really an algorithm, more of a process or procedure.

I think the people that can, have, but perhaps others will chime in. Have you contacted your official support provider, seen if they can provide any guidance?

Is that O/S supported for the client? If so, I'd try reinstalling the client.

Can't answer the connector question but can the job recognize the "inconsistent" data before the Oracle connector or does the database need to do the dirty work? Thinking a logical reject rather than a physical one would do the trick here.

I'm wondering is this is a generic question or a very specific one... as in are they asking about this specific job in this specific sequence specifically? Or is this meant to be more general where X fails and for some reason you'd want to start at X-1 generally.

Required? When you want the failed sequence job to restart from the beginning regardless of what did (or did not) happen in the previous run. Nothing more than that. Perhaps a sequence job failed, you cleaned up the mess, fixed the issues and for whatever reason you need it to start all over again.

Are you certain that your XML will always be that small, fit in that varchar? I was thinking it would be something more like a CLOB or a dedicated XML data type.