DSXchange

saraswathi wrote:...But when i run the job, it's not getting completed, it's running for a long time...

Which is it? Does it run a long time or does it never complete? Have you traced it on the database side? Is it complex query with table scans? If you type "View Data" in the job does it return values?

I have seen that on AIX at v7.5 and it happens very infrequently. I never tracked it down since you need to check locks & processes from UNIX while it is happening.

Since it is complaining about position 17, your file or metadata must be different than what you posted.

No problem, Priyaraj. Someone else might post a non-premium response that will help you soon.

Use a substring expression, in this case the date and time are separated by a " " (space), so the date would be "FIELD(In.Column," ",1)"

If you specify a reject link and turn on the filter stage reject option you should not be getting compile errors. Are you certain that the reject link is marked as such (it should be showing as a dotted line leaving the filter stage)

Hi priyaraj, Y don you try a much simpler solution.... There is no need to use stage variables for this functionality. Instead check condition in the constraint for the link. Use this constraint: not(isnull(required link) ) You won't be getting NULLs from a text file. The constraint should be Trim&...

It can be done with stage variables, but not the way the data is sorted, you would need to sort by materialnum and descending seqnum to make that work.

Make sure the data is sorted, then use a Transform stage with a stage variable that store the last row's seqnum. If it is the same as this row's seqnum don't put a value in "text", otherwise do.

Did you still have a question on how to do this?

The documentation will tell you how to do this, but the steps are relatively simple:

1. Edit the "uvconfig" file
2. while attached to $DSHOME, execute "bin/uvregen" to parse the text file into the one that is actually used by DataStage
3. bounce DataStage

Please remember that an empty string, "", is not null.

Hello and welcome to DSXchange. If you look at the top menu bar you will see the Search button. Please use that to search for "Visual Source Safe" and you will see that there have already been several very informative threads on this subject. If you have any questions after that, you can post them h...

cd to your $DSHOME directory, then "cat uvconfig | grep MAXKEY" to get the current value.

Yep, missed that. And if the key string had a field mark (@FM) in it that would show as well when displaying the key.
When the error occurs again, do a FIX.FILE or uvfixfile to see if there are inconsistancies present in the hashed file, that will rule out corrupt hashed files.