DSXchange

It's hard to tell exactly what is going on with the OP's job as what is posted doesn't make much sense, at least to me. However, in general, it is quite straight-forward to do Type2 SCDs in a Server job and the proper way to do that is what Ray posted - the details first get populated into a referen...

Post the Convert() syntax you've been trying.

OK, then what is the characterset of your target Oracle database?

No, not down but they will need to be 'clean' before you can bring it back up again... and that usually just involves waiting as they typically clear themselves.

They could as long as they are willing to commit every record as it is written to the target database and take the performance hit on the lookup as well. Much better to stick with the hashed file lookup and set it up properly, it really is simple - especially after you've done it once.

Do you mean when the users themselves were created, or when those users have created something else, jobs for example? What kind of 'number' are you seeing?

Wait... who cares if they are in two different schemas? That means nothing, I thought you meant they were in two different instances, especially when you made the dblink comment.

So, what is stopping you from running that query directly in an OCI stage?

That's an important bit of information to leave out.

So, you don't need to implement that actual query but instead duplicate the end result?

Example snippets, please - both of what XML you are getting now and what you would like to be getting.

Why not just - as you said - implement the query? You can run it just like that in an OCI stage.

Of course, why not? What have you tried? I'm assuming the flat file has the key field(s) you'd need. Me, I'd look at a transformer with three output links to a single database stage, each set to the proper update action based on the "tran_type". Can get a little more complex than that if y...

If "upload" means "trigger the appropriate DataStage processing job" then you just need to leverage the dsjob command line API.

Well, then a Help button anywhere inside an open Sequence job will get you there, then find the help for the Job Property we've been discussing. Or open the full help from the menu and use the Index or Search tabs to find it. It *is* there.

Whenever that's the case there, report it.

So... you left the "Log warnings" option unchecked? As noted, it is very simple to solve your original issue and keep that functionality as well.