DSXchange

Sorry, what part is unclear? To track something, you need to store whatever makes it unique, which sounds like the date in your case. Then a lookup tells you if you've seen it before or not.

You might want to add a teensy bit of detail as to how simply going to the Release Notes for 8.1.1 will help here.

Which is your problem, of course. You've got the "two columns" part right as whatever you select needs to have a place to go, it's the key column that's your issue. If you'd read through all of those other posts on the issue you should have seen that Key columns are bound into the "wh...

DataStage 8 server or client?

I was wondering the same thing. Haven't found an ldedit on the system yet, perhaps it's something optional we can download.

Keep track of the dates and numbers you've processed. A successful lookup would mean use the old number (I assume) else assign a new one then store both it and the date.

OK, here's another question for anyone that is playing along in our home audience.

The dev server where this works is running the 64bit edition of Linux, whereas the production server where this doesn't work is running the 32bit edition. Coincidence? Of no consequence? Smoking gun?

Crapola, while that change did cause the "dynLUT" files to move to the new location, it did not solve the issue. It now aborts with: luKeys,0: Could not map table file "/etl1/tmp/FEP/lookuptable.20091024.tdjcnic (size 3506947648 bytes)": Invalid argument Error finalizing / saving...

If you could rephrase / restate your requirements, that would probably be best. Perhaps expand on your examples as well. I for one have no clue what exactly it is you are trying to accomplish and would rather not guess.

Found a TMPDIR where the project default value is empty. I'll try changing that to point to our larger tmp area...

For what it's worth, I changed where UVTEMP was pointing and as I suspected it had no effect on this issue.

Searched for people having the same problem and really can only find similar issues, so I'm hoping someone can answer a specific question or two. Got a production PX job aborting with the following fatal error: luKeys,0: Could not map table file "/etl1/tmp/FEP/lookuptable.20091024.tdjcnic (size...

Why not just do all that in Oracle? And why would you expect adding the overhead of a sort stage sorting on one field to improve overall performance? If you want to go that route, you'd need to sort by all three grouping columns (not just the first one) and somehow make sure the Aggregator knew you'...

54 matches and there's not enough information out there? [sigh]

How many columns do you have defined in the stage? Are any of them marked as Key columns?

And this integer value is... a number of days?