DSXchange

The "XML Best Practices" document can now be accessed through http://www.raywurlod.com

And... ?

What happened?

No, and it has nothing to do with using a shared container. It's an error that was not picked up in 8.0 (it IS picked up in 8.7). You need to check that you are sending a nullable field into a Sequential File stage but have not provided a NullFieldValue property to tell that stage how you wish null ...

Are you using DecimalToDecimal() conversion function?

Possibly also the temporary directory does not have enough free space.

Resist stupid requirements.

The Checksum stage gives no additional information about what is different.

Not only do you need to import the table metadata (which you have done) you also have to register interest in analyzing that table in the project in which you want to perform the analysis. I believe it's this step that you have missed.

You'll find it easier to use Change Capture or Difference stage.

If it is not a good idea then why datastage is allowing to design and run in that way. Ideally engine should throw error. There are some - infrequent - situations where this type of design does make sense. I have used four such job designs this week. The data in the two streams were related, but in...

Try using telnet to the DataStage server with port number 31538.

Can you open the web console for Information Server (which uses port number 9080 on the services tier machine)?

I agree with Arnd. Create a Surrogate Key state file.

In the Transformer stage use the NextSurrogateKey() function.

You will need to configure the Transformer stage properties (Surrogate Key tab) with the location of the state file.

That proves that dsrpcd is running. Using the port number is more reliable (imho) than the service name.

Can you connect to the DataStage engine machine by some other means (such as telnet)?

How are your Engine Credentials configured?

In any case, it would depend on how and where the environment variables were encrypted, and with what utility.

Try netstat -an | grep 31538 instead.

If this finds nothing, then dsrpcd is not actually running, and you'll need to diagnose why not.

Perhaps there were no exceptions?