DSXchange

Hehe. One of the first thing we did when we got PX for 6.x, we tried the Reporting Assistant. Failed. Cried to Support. "Oh, we're surprised you're using that... use MetaStage instead, that's the tool that is replacing this depreciated feature." That was 6.0 (and soon after that, we got 6....

Well, if you have pre-sorted the data before you landed to a dataset, that information should be propogated to the Join stage, overriding its internal sort function. And thanks to the 'keep things simple' option set on by default (which I forgot the formal name for) (Something with Combination in it...

Good question from the young gentleman in the back.

The second reason: Memory access Vs Disk Access. Join stage MUST have the data on the disk before it is used. Lookup doesn't.

You're having access problems with your Project folder for some reason.

7.5.1a should be available by now. Check it out.

Ensure that your Datastage paths are defined before your Oracle paths. This is true for all database setups within "dsenv" file.

Actually, 6.x.

Partitioning is NOT eliminated. It is just a matter of: "If you need to repartition this data, feel free." instead of: "You can not repartition this data." Sequential stages must repartition, so that's why you got the warning when you told it (by default) to not repartition, and ...

And no, do not expect support for Windows 2000. Windows 2003 only. Sorry.

Segmentation Fault - http://www.wlug.org.nz/SIGSEGV * The pointer is NULL. * Address not mapped to object (eg, the memory is unallocated, and unmapped by the OS) * Invalid Permission for mapped object (accessing memory that permissions deny). I suspect that you will need to ensure that you are defin...

There is a known issue with JobMonApp related to a job crashing in an unusual way -- for some reason, it would take JobMonApp down with them. There are a number of patches available, but again, as Amos mentioned, it does not appears to resolve the problem. Go to $APT_ORCHHOME/java and take a look at...

Do your own job, or pay someone to do it for you. I refuse to help people who expect the complete code, and refuses to understand what is going on here. There are wonderful advices that a person who is capable of using PX can easily utilize to create a job. Do what you are hired to do, or pay someon...

This sounds like a Client-specific (GUI) bug. What operating system are you using? What's the first name of your support person?

You got that correct. Thanks to the way things are designed -- DataStage would determine whether any specific stage needs to have pre-sorted data. Stages such as Join, Merge, Aggregation, et cetera -- all have their own hidden sort trigger within the framework (you will not see any sort request on y...

1> For a particular type of record if the record count exceeds threshold value the job shud abort. (threshold value is defined in job parameter) One solution: Transformer, put constraint and specify the "abort after row" value to the required value. 2>Also job shud write a specific messag...