DSXchange

You want to do this in DataStage or in Oracle? In the job, an If-Then-Else derivation would be perfectly fine:

Oracle itself doesn't need double-quotes for "special characters" but you need to use them to break the rules for what is allowed where. For example, you can use a # anywhere in the password except as the first character without needing to quote it. However, if you want to use the # as the...

Been discussed here alot, search for "Computed blink" to find the conversations.

Define "not working" please. Post any applicable error messages as well.

The number doesn't matter, it was a bug from simply having it on that Arnd is worried about. Make sure it is off/disabled for this particular job and see if that helps.

Interesting... never noticed that in the stage title, and all of the documentation simply references the "Sequencer" stage. I'm guessing the "condition" may be specific to the internal setting - All or Any - but it doesn't really matter in the Grand Scheme of Things. Now we'll kn...

Right... use links from the transformers to capture both logical and/or physical rejects and then transform/land them after that any which way you like. By 'logical' I mean records you reject before the target using constraints, 'physical' would be ones the target rejected and barfed back up. Be awa...

There are other APT variables that may help, check this post to see if anything there works for you.

Just how same is the "same error" you get after changing the APT variable? Exactly the same as in it still says "the max block length is: 131072" or just that it is still "too big" but you see the "max" changing?

I have no idea how to handle something that big, sorry. Hopefully someone else does.

Your input record length is over 4 billion bytes?

It always names them "TRANSn" rather than using your names and "TRANS2" would be the second transformer in the job. And the specific "RT_BP*" directory for this problem would be RT_BP923 - the Job number is explictly mentioned in the phantom error message.

Right, you seem to be a little confused about "waves", they've always been there.

The biggest problem with 8.0.x is the sheer bugginess of it, hence the advice to skip it entirely now that 8.1 is out and go straight to that.

He wanted to know if you have Windows "SP2" - Service Pack 2 - installed on your client pc. And if this is strictly your problem or if others are seeing this as well.

So this is an 8.x error rather then from the 7.x side, yes? Search the forums for the "Failed to" part of your message and see if anything matched posts help.