DSXchange

How about clearing the project entirely then importing without the executables, using "Import Selected"?

It's not in 8.7 and is unlikely ever to be in the product.

In 8.7 you may be able to identify the jobs using Quick Find or Advanced Find in Designer if there is some sufficiently common characteristic that you can identify.

Did you Search DSXchange? This should always be your first action before posting.

There's one solution here, for example.

Design a simple job (or before-job subroutine) that will test whether Oracle is "up", perhaps using tnsping command.

Information Server 8.5 can run with DB2 9.5 or 9.7. What DB2 software you will need on the engine tier will depend on what you want to do but, in general, the client software is required. You may also need DB2 Connect. As noted, you may well have the client available from your services tier. But, ye...

Are you sure it's not ^@ (Ctrl @)?

^@ is how ASCII codepoint 0 is represented. This is the default value of APT_STRING_PADCHAR; the character with which Char data types are padded to length.

Why did you re-post this server job question, which you have already asked, in the parallel job forum?

Can you please check PATH, LIB and LIBPATH environment variables?

You can delete the "instance" entries from RT_STATUSnnn and you will find that the instance log entries magically disappear.

It appears that Designer looks in the local (project) repository. Director looks in the unified metadata repository (XMETA).

Try writing out the logic in English. The nature of the required self-join may well become apparent when you do this.

Just to confirm, you only get one DROP specification. Or only one KEEP specification. Not both.

No.

But you only have to do it once.

I suspect the question is about how to specify the columns to be considered as keys to be considered when detecting change, to which the first answer (read the manual) is apposite. In the manual you will also read the necessity to partition and sort the data.

Unsigned TinyInt (uint8) is the closest DataStage approximation to Bit.