DSXchange

I can't. We're missing some critical information here. It won't abort after 50 if you run it unlimited. Is this perhaps a Sequence job you are talking about or are you running a 'stand alone' job directly?

Actually, that 'trailing' or extra slash in the pathname doesn't hurt at all. At least I've never seen it be a problem, so wouldn't focus on that. [shrug]

How are you setting the Invocation ID in the Sequence job?

But my client is adament on not to give these select privileges on dba tables to ETL user account as they are against the Sox compliance . I'm sorry, but that is just so wrong and shows a poor understanding of what 'Sox compliance' means. Without those privs you are SOL. So, it's ok for the ETL use...

Actually, it defaults to 50 when run from the Director - and unlimited when run from Designer regardless of your Director limit.

Exactly. Let the stages generate the sql. Use a Timestamp datatype for the Oracle DATE fields. You'll be fine.

As noted - why write this when a built-in function already exists to do this?

True - checking that for some reason would shut down the functionality of [b]all[/b] tags. I would [i]guess[/i] you'd only do that if you were tutoring someone on what the tags would look like in your [color=red]still evolving post[/color]... or some such.

Why complicate it so much? Three variables like so: svNewKey: in.field1 : '|' : in.field2 : '|' : in.field3 svIsDup: svNewKey = svOldKey svOldKey: svNewKey Make sure you have a decent initial value for the stage variables and you handle nulls in svNewKey if any of the three fields are nullable. Then...

I work with the boy and I know I'm missing something. I was just too caught up in other crapola to even know he was struggling with this yesterday... need to go downstairs, smack him upside the head and figure out what's going on here.

Silly me. Based on your assertation that 'it worked in the Manager' I assumed you knew you were supposed to use an active stage and were actually doing that in your job. Obviously, that's not a fault in the routine itself, but how you were calling it in your job which is what I was suggesting all a...

That's where I was trying to get to, Ray. Eventually. Just because you use a Sequence doesn't magically mean you can't have duplicates. That could be the case if the target table started off life empty and you never had any issues with the Sequence itself, like some kind soul resetting it for you. B...

Rotsa Ruck. I've been using it off and on for quite some time now and can't even see Ernie's level - it's that much further up Mount RTI.

Define 'call Java code'. What / when. Otherwise, the only appropriate answer is 'yes'.

Code tags work, not sure what your issue was. Each word has two spaces between them. Each word has one space between them. Thank you for confessing your sins, My Son. It helps other supplicants who come here searching for answers from going astray. With your original stage variable order, you were d...

Then the issue is something you haven't mentioned yet. How about posting the sequence object definition? Curious what some specific attributes are: Increment By Max Value Cycle Fun stuff like that... but please post them all. I'm also curious about your 'very strange' remark - when you ran the job 3...