DSXchange

No about it. Yes.

Sorry, but that's not why we're here.

Noob.

kumar66 wrote: Its version 8.0.1 .

Known to be... buggy. Contact your official support provider and see if there's a patch you're missing.

Seriously consider upgrading ASAP to the latest 8.1.x release.

Then they are getting comitted. Are any rolled back at all? What 8.x version? Have you asked your official support provider the same question?

The document doesn't really give good example.. They should include proper example into the doc. Of course, they "should" all kinds of things in the documentation that they aren't. However (and I should have quoted it so it was more obvious) I was specifically replying to the question of ...

probal wrote:I fear it can't be done.
datatage can't process column names having '-'.
In oracle u can do it. but even then datastage will not support that column

Not quite true... and the answer depends entirely on the (currently unknown) target.

I reset the padchar to x'20' where it was prior to the fix pack. You phrased this differently here. If you never had PADCHAR set, then I stand by what I said. If it was explicitly set to space and the fixpack set it back to null, then you do in fact have an issue you should report to IBM. I underst...

We saw DataStage 8.1 replacing spaces with x'00's after applying some patches. We haven't been able to pin down the cause but we know we had blanks before the patch and x'00's immediately afterwards. Has anybody else encountered this? If so, have you determined the root cause? Noted the same thing ...

Not sure how anyone could help - you identified and corrected the problem. And x'00' is the default pad character unless you set that APT variable to override it. Sounds like you've been relying on a bug and they finally fixed it.

Post samples of your actual input data, please.

That should happen automatically as long as two things happen:

1. No intermediate commits are done
2. Job actually aborts rather than finishes with warnings

Someone else some time ago posted about how simple the encryption was and even the details on how to break it. They were very proud of themselves. Like it was meant to be hacker-proof or something.

Does your company have any kind of an "Enterprise" scheduler?

Don't know how you can suggest that without knowing the characterset of the target Oracle database.

What's your target?