DSXchange

So I have set the ulimit on OS level and in the dsenv file

ulimit -d unlimited
ulimit -m unlimited
# ulimit -s unlimited
ulimit -s 4194304
ulimit -f unlimited
ulimit -n 4194304

In the uvconfig file I have set the 64BIT_FILES 1

Database to Hash - about 220 Mil records to be written to the hashfile

The Jobs runs up to a point then it just hangs - no errors - the filesize is round 2gb - so it has reach the limit for 32bit - but it is set to 64 bit -still it doesn't grow.

We have recently migrated from 8.x to 11 and it works on 8.

Is there anything else that I can do , did I miss a step?

(Info above it what I could find in this Forum and IBM's website)

Thanks in advance

I would ensure to do a regen after adjusting the uvconfig file. Recycling the engine is mandatory too. Below the info from IBM support


http://www-01.ibm.com/support/docview.w ... wg21637567

Before Ray comes along and says something, they are hashed files not hash files.

I would also note that "best practice" suggests you should only set the one specific hashed file to 64bit, not every single hashed file on the server, which is what happens when you change that uvconfig option. Best to stick with option #2 in the posted link IMHO.

Did the uv regen
Added the file via the command line.
It gets up to 2.1GB and then just hang there - job doesn't fail - doesn't complete.
Could it be a limit in version (11)?

There's no new limit in version 11.

As Craig noted it is unwise to set 64BITFILES in uvconfig, as this will force every hashed file to use 64-bit addressing.

Better would be to delete your problematic hashed file, and recreated it with the -64bit option.

On your install media you will find a Hashed File Calculator in the unsuppored utilities; this will allow you to specify a size and generate a command for creating the hashed file.

The 64BITFILES option in the uvconfig file is working

We missed one of the regen steps - when we did it - it worked fine.

Thanks for all the help

It's still by far the poorer choice.