DSXchange

As noted, this is almost cetainly an issue of invalidated indexing in the Repository. Therefore the most likely cure is to gain exclusive access to the project and issue a DS.REINDEX ALL command therein.

This is not about locks; it is about shared memory. An ipcs -m command will show the shared memory segments in use; any with a key beginning 0xade are DataStage shared memory segments. It will also show that the permissions on them are tight (rw-------) so that you must shut down DataStage using the...

pi is irrational. i is imaginary. i squared = -1.

Easiest would be to read the file and pass its value into the second job as a job parameter. You would do this with an Execute Command activity in a job sequence.

Try searching the forum for "vertical pivot", for that is what you are trying to accomplish. It probably is easier to accomplish in a server job than in a parallel job, but can be achieved in either.

Yes, that's them.

There are three different kinds of custom stage you can create in (for) parallel jobs. Any volunteers?

Alas, you'll need to kill them all!

In version 7.5 and later, DataStage Sort stage will outperform UNIX sort.

Make sure that you have PLENTY of scratch disk configured, to sort a file of this size. Use multiple file systems per partition for scratch disk, to improve disk I/O throughput when using scratch disk. More is better.

You could write a strong letter of complaint to Oracle bin Larry for not following the SQL standards that the rest of the world follows.

You could split the stream into two copies, run one copy through a Promote Subrecord stage and join the two copies subsequently, selecting appropriate columns from each input to the Join stage.

What error message is returned when you use
(Have you tried it without the terminating semi-colon?)

Try also setting the Default property for the appropriate data type.

The error is from Teradata, not from the Modify stage.

Please document the Modify stage specifications that you have used.

Please also import the table definition from Teradata using orchdbutil (from the Import menu). Advise whether that is the same as the one you've used in your job design.

It's an alert. DataStage is warning you that, in going from a scale of 10 to a scale of 0 you are likely to lose some information. It is also alerting you to the fact that it (DataStage) does not fully support numeric floating point decimal, and that therefore it is adjusting the scale so that the n...