DSXchange

Yes, I think that's what I was trying to convey. I've always installed MWB with BG.

What I meant was, does the UNION statement in DataStage still extract data from the database, even though it throws the warning?

Can you also check in the job log that the SQL being used is precisely the SQL that you provided?

Only by stopping the job.

Is it really an error? That is, does the UNION statement still extract from the database?

Also check TMPDIR. Try pointing them to a location with much more space. Check while the job is running. Often /tmp is undersized for DataStage - using a different file system (with more space) is recommended.

The value is represented by Char(0) or UniChar(0). You can use either of these representations in functions such as Convert(). In particular, this value is not the same as NULL (even though it's referred to in ASCII as "NUL").

As far as I have been able to determine Business Glossary allows you to view the (simpler) Business Lineage without a Metadata Workbench licence (though, as Ernie observes, it has to be installed) but, if you want to drill down via Data Lineage, then you do need a Metadata Workbench licence.

Identify the "unknown character". Perhaps convert it to hex.

No. You need 8 bits to represent -128.

Capture a before-image and compare.

Scratch disk is usually automatically cleaned up when jobs finish normally, but not if they abort.

Solution: create job designs that don't abort.

It doesn't matter what it's a link to. It's there.

Always answer "Would you like to set it up?" in the negative.

DSAttachJob(), DSGetJobInfo() and DSDetachJob().

What code page is used by the Teradata table?

Match that (even though the names may be slightly different) throughout your job design.

Beware that xFFFD might also be a byte-order mark, though I wouldn't expect to find this in a record in a database table.

So you have binary values that are not EBCDIC code points. Messy. Can you specify the first two bytes as SmallInt rather than as part of the string?