DSXchange

Try this

You can find some routine posted, for periodic clean up of project directory. You can make use of it.

You tell us, why you need the sort stage to store the data in the file. If your requirement is to find the max of the group, and that too, if you already found using the 2nd aggregator, I dont find a need to sort stage. If you give some example of what you expect, and what you get if sort stage is b...

We have such one but not exactly the same. We maintain a count in a table. A .SQL file been called each time, which will update the table, by fetching the max of the count and add 1 and update the same.

orchadmin -dump should be more appropriate for your requirment.

@OUTROWNUM can be used only if the number of records are predefined. Tail stage can be possible used based on your requirement.

I may be wrong but i think ray is busy these days and gets lesser time to spend with us. thanx a lot anyways Ray for the effort and support you have given to us. His rate is still 9-10 post per day. Some time I find him posting more than 50 post per day. You cannot expect him to work more harder. :D

Or Index() in transformer to find the and replace with the given string. If not sure about the number of occurance, you can make use of Dcount().

ALTER TABLE and DROP CONSTRAINT in the before sql and ADD CONSTRIANT in After sql.

1) As already mentioned, the hashed file which is used for lookup, can be replaced by either a lookup file if the data can fit into memory else other stages on Sparse lookup. There is not hashed file in PX. You need to recreate it in any of the available format. 2) If you want to collect back all st...

So what is the error that's been thrown out?

Congratz Ray!!!

Roy- I guess you have missed this.

It is actually populating the records with the intermediate values between the to and from range. But again it will chalange the performace for the 1million row lookup. But is has advantage of equality predicate.

However, If need to have a reject handling based on the given business logic even in future, you can add a transformer. If there is no functionality required, its better to remove, because it will always consume its own resource.

You can capture the database errors like SQL CODE and SQL ERROR from the job by extendending the reject link with these column enabled using RPC.
If you need to load the logs available from datastage, you can use dsjob -logsum/-logdetail/-lognewest functionality.