DSXchange

srini.dw wrote:In my case I got a requirement to delete dataset segments which has names such as PX_BEA.ds.dsadmin.DEV.0000.0000.0000.65e7.cf771bfe.0000.b324c6a7 located in is/node1/dataset.

A single question back to you: WHY?

What in the world does your reply have to do with the question here?

I wouldn't make any such assumptions. Look into changing those values only if you have "issues", I wouldn't worry about that out of the box.

There's no way to know what's going on without access to your system, I'd wager. In your shoes the first thing I would try is exporting and re-importing the Sequence job so it get rebuild in the repository, see if that helps.

Why not simply read the documentation that came with the product?

So, you are actually talking about the uvconfig file, yes? I would imagine that the default values are the 'recommended' values, which is why they are there. I for one have never seen a need to change them. I certainly hope you did not move that file over from your old, completely different operatin...

Done.

You can't run a BASIC routine from any database stage and a job cannot reset itself. You'd need to do this in a separate step using something like a Sequence job. And would never reset a job after it ran, you lose too much diagnostic information that way. Reset it before it runs the next time, just ...

And by the way, masking != encoding. Something encoded can be decoded while masking is a one way street. A checksum is also a one way street, so not a good candidate for 'encoding'. If a database is involved in this process, you should check to see what functions they offer, for example Oracle has t...

zulfi123786 wrote:Aggregator is the one which i presume is causing the issue which as said creates a hashed file and then operates on it.

Sorry, I've edited my earlier post to be clearer - it is the Merge stage that uses hashed files and is what is failing, not the Aggregator.

Clearing &PH& doesn't "unlock" anything. Have you contacted your official support provider yet?

Suggest you explain in words how you get from that input to that output. What is your business rule?

swapnilverma wrote:I had to HIJACK this thread. I think it better then creating new one ??

No, you didn't and it is never better. Always start your own thread so you have full control over its destiny and if you really feel the old thread adds value, link to it.

srinivas.nettalam wrote:

chulett wrote:Where are you looking at the file, on Windows?

Yes

Yah, that was a hint.

How many lakhs? How wide are the rows? The Merge stage uses hashed files under the covers and probably blew past the ~2GB barrier they inherently have.