DSXchange

Usually, any tool (like Toad) should have the ability to display that. Worst case, ask your DBA. No clue about SQL Server but for Oracle:

Do you know what the code page / characterset of your source & target databases are?

Golly... first.

Much as I'd like to see peoples, I'm not going to be there.

Have no way to check but (from what I recall) there should also be an associated style sheet that it uses to generate the report and that can be modified as well.

So... resolved?

Note that I didn't say it couldn't be done, just that it was 'invalid' and that nothing was broken as in needing to be fixed. Sure there are workarounds like editing the version number but there's no guarantee that even if you can get it imported that it will actually work. And don't expect support ...

By now you should know that CHAR fields are always padded to their full size and the environment variable that controls that is APT_STRING_PADCHAR. By default it is set to '0x00' (aka hex zeroes or low-values) which is what you are currently seeing. Add $APT_STRING_PADCHAR to your job and change it ...

There's nothing to fix here, you are attempting something invalid as there's no backwards compatability - especially from 8 to 7.

Answer my question, please.

My developers want to have one hash file that would be located in two separate directories. I'd be curious eactly what this means. The distributed hashed file that Ray mentioned would mean there would be two "halves" of the hashed file in existence but it would still be accessed as if it ...

Hmmm... that's just the external API - dsjob.

Is this perchance... in a CHAR field?

rajadommeti wrote:There will be a job (job_for_ever) running 365 days, every day at 7 AM it has to call another job ( Datastage_WS_job)

This 'forever job' sounds suspiciously like cron to me.

Wait... the parallel transformer doesn't support the concept of link ordering?

I was wondering if that was the only difference... not sure how useful that turns out to be as I don't recall ever seeing a date with internal spaces like that. [shrug]

Ah well, at least now we know.