Hi,
i am trying to convert a Hashfile from 32 to 64 bit.
I created a hash file,using Account Name.
This hash file contains 60 Million records,with 500 bytes of each record length.
While, conversion,it shows an error that
there is No space in the device.
Resize: Error on hash file not resized
mkbdfile: error initializing file.
Using HFC.exe,i generated the syntax and try to run the command from DSADMIN.
code:SETFILE hashfilename hasfilename OVERWriting
RESIZE hashfilename * * * 64BIT
we have already sufficient disk space,but still its giving the error.
if u need more info,please let me know.
any ideas?
thanks
problem with converting to 64 bit hash file
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You have run out of space on the file system where the hashed file lives. RESIZE makes a copy of the hashed file, so you need another file system that has at least this much space - plus the overhead of the larger (64-bit) internal pointers.
RESIZE has a USING option that you can use to specify a file system (that has lots of free space) on which the temporary copy can be placed. For example, assuming /usr/tmp were such a file system:
Incidentally, the correct terminology is hashed file, not hash file.
RESIZE has a USING option that you can use to specify a file system (that has lots of free space) on which the temporary copy can be placed. For example, assuming /usr/tmp were such a file system:
Code: Select all
RESIZE hashedfilename * * * 64BIT USING /usr/tmp
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Thanks ray,ray.wurlod wrote:You have run out of space on the file system where the hashed file lives. RESIZE makes a copy of the hashed file, so you need another file system that has at least this much space - plus the overhead of the larger (64-bit) internal pointers.
RESIZE has a USING option that you can use to specify a file system (that has lots of free space) on which the temporary copy can be placed. For example, assuming /usr/tmp were such a file system:Incidentally, the correct terminology is hashed file, not hash file.Code: Select all
RESIZE hashedfilename * * * 64BIT USING /usr/tmp
but i have sufficient space on device.
Try this to prove the point that Ray and Craig are trying to make. Do an ANALYZE.FILE to get the modulo for the current file. Then do a "CREATE.FILE NewFile DYNAMIC GENERAL MINIMUM.MODULO {mod} 64BIT". This will create an empty file that is presized. If you can create the file, then you can issue a "COPY FROM OldFile TO NewFile ALL"
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
... provided you've got enough disk space to create the new hashed file, and you use MINIMUM.MODULUS (not MINIMUM.MODULO - Arnd is living in the past, static hashed file, world!).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.