DSXchange

The thing about the machine logs is that you don't know what's in them till it's there. I believe that archiving allows you to "go back" when trying to diagnose some kinds of recalcitrant problems. Largely, though, the machine logs are XML format files containing performance data sampled a...

Do all jobs fail on node 1, or just this job?

Enable the environment variable that tracks job startup status and run again. Does the score get distributed successfully?

Using a Complex Flat File stage.

Please do not waste our time by posting the same question in multiple fora.

Using what kind of job? This is important - it's done in different way in different job types.

Have you imported the table definition from the XSD or otherwise from the XML itself? How have you set your xpath expressions?

Use Complex Flat File stage. (I assume that the file has been landed on your UNIX server.)

My company doesn't like demoting messages and also does not accept any warnings. You're between a rock and a hard place. Entire partitioning will yield incorrect results in your job design. The responst to "doesn't like" therefore has to be "tough". Check partitioning in the sco...

Ignore the message. It's only alerting you to the fact that shared memory will not be used because not all keys are on all nodes. Use a message handler to demote to informational. Next step is to look at the score, to see what partitioning (Auto) is actually giving you. The Sort stage requires its i...

Your main problem is that sparse lookup is not supported into Sybase. Use a Join stage.

This is an unusual message. What is your Transformer stage doing? Can you please post the exact, and entire, message, so we can be certain before offering advice? (Auto) will probably achive optimum partitioning in this job design. I'm only curious about where it thinks that Entire might be appropri...

The outcome will be a consecutive sequence of the same numbers on every node in the configuration. No uniqueness.
Have the sequence start with the partition number (possibly with a constant offset) and be incremented by the (constant) partition count.

nayanpatra wrote:I would also like to know which database you are using.

Given that the subject specifies "using Oracle Enterprise stage" I would hazard the guess that the database is Oracle.

Get your DBA to monitor what DataStage is asking Oracle to do (that is, to monitor the session).

In that case you should have no difficulty inserting as many rows as you can generate. So it looks like the issue is generating the records, rather than actually inserting them. Why not create a Transformer stage with one output per business rule, and bring these back together using a Link Collector...

It is not possible. For the repository, services and engine tiers the only supported Windows operating system is Windows Server 2003.