DSXchange

This is so not a DataStage question, but yes that's one way to accomplish that and there are many resources out there for you if you Google ".netrc file". This for example, or this. RSA keys are another solution.

Not sure why you'd need an 'escape sequence' for a trim... you should be able to call Trim() with the character surrounded by the 'other' quotes, i.e. "'" or '"' for example. Is that what you needed?

What evidence do you have that it actually ran?

Your only option in that world is dsx exports of your objects combined with the external versioning tool of your choosing, like ClearCase or VSS for example.

As long as you're supplying all keys fields, which it sounds like you are, it should work. Standard advice - make sure your values actually match, are trimmed properly, etc etc.

Suggest you start your own thread.

Right, sqlldr with DIRECT=FALSE is a 'conventional load' and does normal inserts, so the commit interval plays a role. When DIRECT=TRUE there are no commits done.

No clue. Something must be different between the two environments, the hard part is going to be figuring out on your end what that difference is. Best suggestion would be to open a case with your official support provider, the ones being paid Big Money by your company for just this sort of thing. An...

:? Can we get examples please? Not words, but example values. Show us a small number of values from all three tables and then how they would all fit together. Forget the "few other columns" part, just the "keys". Maybe then we'll have some idea what "get Table 1 sequence num...

Sorry, but that's not going to work. It won't do the multiple 'levels' or iterations of substitution / resolution you're looking for. It does turn your job parameter into the string you passed in but it's just a string at that point, it doesn't then know it then needs to resolve the stage variables....

But now sql code in the reject link is -1. It should be 00001. How can i overcome this? Nothing to overcome, in a way. They are reported as negative values so what you think "should be 00001" will be "-1", likewise a "02291" will be logged as a "-2291" as you...

You are encountering a "known issue" - reject links won't work correctly unless the array size is set to 1. Andy, isn't that strictly a Server issue? I don't see anything like the OCI 'Array Size' option in the OE stage doing Write Method=Upsert. What am I missing? :? Never mind, answerin...

As far as I know, you'll need to read it as a string / varchar field and then convert it to a decimal 'in job', taking the trailing sign into account.

There's no "workaround" per se, if you restart an Aborted/Restartable Sequence job and you use different parameters, you will get that message logged. As noted, you'd need a mechanism to not dynamically generate a new one but use the last one generated instead when you find yourself in a '...

Duplicated that. There should be a log message before that with the reason why. For example, my example: Oracle_Enterprise_child,3: Unable to use a record for update. Logged just before that: Oracle_Enterprise_child,3: Open failed for update: update is: INSERT INTO CRAIG_TEST_CHILD (CT_CHILD_KEY,CT_...