Hi,
I am trying to run a job which creates a HASH file from a table, there arearounf 12 million recordsin the table. In the log the status shows as waiting for the job XXX to start. The status shows as running only after a period of 30 minutes. I am using the default hash file options i.e. Type 30(Dynamic).
1.What are the best options followed for faster completion of the job?2.Should the Allow Stage write cache be enabled
3. Is it better to delete file before create
Any help appreciated
Hash File Options
Moderators: chulett, rschirm, roy
Hash File Options
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
-
- Premium Member
- Posts: 385
- Joined: Wed Jun 16, 2004 12:43 pm
- Location: Virginia, USA
- Contact:
If you are just writing to the hashed file, then enable write cache.
Chuck Smith
www.anotheritco.com
www.anotheritco.com
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The write cache is good. What you get is writing to random locations in memory rather than writing to random locations on disk (within the file structure, of course). Once all rows have been written, the cache is flushed to disk in group order, which is maximally efficient I/O.
You can preallocate disk space by specifying MINIMUM.MODULUS when creating the hashed file. You can also preallocate disk space by specifying a static hashed file (type 18 for example). The latter course is indicated where the number of rows is known in advance and unlikely to change - or unlikely to change much - over time. Preallocating disk space (that is, preallocating the number of groups) will be beneficial even if write cache is used.
You can not use write cache if you're also reading from the hashed file while it is being written to.
You can preallocate disk space by specifying MINIMUM.MODULUS when creating the hashed file. You can also preallocate disk space by specifying a static hashed file (type 18 for example). The latter course is indicated where the number of rows is known in advance and unlikely to change - or unlikely to change much - over time. Preallocating disk space (that is, preallocating the number of groups) will be beneficial even if write cache is used.
You can not use write cache if you're also reading from the hashed file while it is being written to.
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
The number of rows cannot be predetermined (So i wont be able to use Static Hash File). For preallocate disk space by specifying MINIMUM.MODULUS do I use the standard formula's or is there any other way we can optimize the performance?
The number of rows cannot be predetermined (So i wont be able to use Static Hash File). For preallocate disk space by specifying MINIMUM.MODULUS do I use the standard formula's or is there any other way we can optimize the performance?
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
-
- Participant
- Posts: 22
- Joined: Fri Oct 15, 2004 11:53 pm
- Location: Bangalore, India
- Contact:
"Delete file before create"
Hi,
If we enable "Delete file before create" option in the hash file and run the job repeatedly, we are getting the following error "Unable to delete. The file is allready in the VOC list". This happens with some of the hash files. Can anybody explain Why?
Thnx
Subramanya
If we enable "Delete file before create" option in the hash file and run the job repeatedly, we are getting the following error "Unable to delete. The file is allready in the VOC list". This happens with some of the hash files. Can anybody explain Why?
Thnx
Subramanya
Define "repeatedly"? I'm guessing the delete is failing because it's actually still in use when the attempt is made.
Are you sure it doesn't say "Unable to create" instead?
ps. You really should have started a new post on this specific topic, rather than piggy-backing on the end of an existing (but at least semi-related) thread.
Are you sure it doesn't say "Unable to create" instead?
ps. You really should have started a new post on this specific topic, rather than piggy-backing on the end of an existing (but at least semi-related) thread.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers