DSXchange

You'd have to code the routine to write the OracleCmd to the log yourself for it to show up, using DSLogInfo from what I recall.

So, what exactly happens when the routine runs that last SQL example? Is it just that you are losing the single quotes or is something else going on? If you have anything from the log showing specifically what it tried to run, that would be best.

Julius Lerm. Really nice guy.

He came out to help me on something WAY back in the day and then we both needed some help from Ernie.

I'm curious if you tried anything in those other threads or did you just read them? Oracle doesn't like double-quotes and you typically preserve single quotes by enclosing them in single quotes, which one of the linked topics mentions. Or sometimes you need four for each one! There is also syntax to...

Was thinking the same but hoping for more better data to confirm.

Why is the third / "GHI" record in the expected output? I'm also curious if you have any examples of real data, not something that's obviously made up and which I worry may be far too simplistic. I'd like something that better illustrates your "falls within" requirement rather th...

You might want to explain a bit what that means in your world so people can provide better targeted answers...

Sounds a bit like you are reinventing the wheel. :wink: What you've got is a Type 2 "Slowly Changing Dimension" and there's an actual stage dedicated to them. Regardless if you use it or not, there's no need for two jobs or anything "after SQL". If you decide to not use the stage...

As a moderator I can only do the former. The latter requires someone like Rick or Andy.

Texted Rick...

I want it to start from 1 for each job run. Then it would seem you do not have a need for any kind of surrogate key 'generator' but simply need a counter. At its most simple, you could use a stage variable for that, initial value of zero, increment for each record... as long as you handled the part...

That isnt kept up automatically. I seem to recall this being true all the way back to the 3.x versions that I started with... it had to be manually incremented to make use of the field which of course meant it was hardly ever (sometimes also known as never) 'correct'. Guess that hasn't really chang...

So these kind of issues are always about the character sets involved, source versus target. Any tool that does this kind of work needs to know both so that, when they are different, it can translate the characters properly between the two - unless they haven't been properly specified. When it thinks...

There isn't really any need to repeat your question.

I'm not aware of any mechanism but perhaps someone else is. Seems to me that, worst case, you could build a job to dump the contents to a flat file.

If it doesn't matter which records go where, I'd look into the MOD function based on the record number... which you can generate if needed. Mod by 10 and assign any one of the remainder values to the 10% link and the other nine to the 90% link.

Not sure why you felt the need to start a new post when you already have one on the same subject.

Anywho, you just do literally what it says. Taking your example:

Command: /home/dsapp/scripts/Handle_Overrun_job.sh
Parameters: /NOLOG/ dst #DBPassword#