DSXchange

It could also mean it was "not runnable" because that invocation was already (aka still) running from a previous invocation of the job.

Unfortunately, this forum is not moderated.

That sounds like one solution, a Mod() would have worked as well, I would think. Or a simple counter checking against the parameter value. As usual, more than one way to skin the cat.

It's not all *that* different, you simply reset on a count rather than a key change.

Because technically an XML file isn't a flat file with rows and columns, it's a stream of data that could very well just be one long "record". Sometimes it can be read like one with success but more often reading it in that fashion just plain ol' horks it up. Best Practice is to avoid the ...

Yet another chance to use stage variables to control that, something very similar to what was just posted here I would wager:

viewtopic.php?t=135971

They noted that they've already tried that and had issues. From what I recall, it can depend on your platform and mail server, they don't all work the same way. Some want a comma between the files names, some want a "comma space" and I believe I had one where it took a semi-colon. Still, z...

Hence the problem. If you really want to build 'environment neutral' solutions for date/time handling, you'll bring them in as strings from your source, ensure that string source is in a valid format for the target and then use TO_DATE() or TO_TIMESTAMP() in your target sql with a matching format ma...

And just to further discuss this, one of the last clients I worked with had a 64bit development and test environment but a 32bit production environment for some silly reason. Entire partitioning on their loads, which involved a significant amount of lookup activity, worked fine small or large volume...

But definitely keep it in mind for when you are doing 'huge' lookup volumes, I've seen people run into issues in a 32bit environment when they did not follow that advice.

Tell us exactly how you are handling that value: data type in source and target, transformations, IConv/OConv, source and target sql, etc etc. We would need an appropriate level of details from you in order to be able to help in anything more than a very generic manner.

More about your job design and what is going on in your target than your source query, I would wager. As noted, details would be appreciated.

Specifically wondering about the syntax in the SP stage, the anonymous block it generates and what parameter markers are being used. Don't recall, but if that stage uses the Oracle numbered parameter markers, you should be able to use the same column more than once easily. If it uses the '?' positio...

StringToDate() followed by DateToString() using an appropriate format mask in both cases. Don't have access to my reference materials but off the top of my pointy little head, %yyyy-%mmm-%dd and %yy-%mm-%dd respectively?

Is this a PX job as per the forum you posted in, or is this a Server job as you marked the post?