<<Over the past few weeks we have begun to experience severe 'hangs' on
one of our production systems. Investigation has shown that dbputs to a
detail set may be the culprit. Normally, updates are performed
immediately but now the delay can be from 1 minute to 10 minutes. During
this time glancexl shows the process to be using a lot of disk i/o (but
there is no unusual physical disk activity). Other processes attempting
to write to this dataset are IMPeded (there is item level locking on all
processes).
 
Glance also show potential memory bottleneck (more memory is on order)
but this does not appear to be a factor in this problem.
 
The detail set contains 2.9 million records (cap: 3.6 mill). There are
two search items, the first is to an automatic containing 5.0 million
records (cap: 5.6 mill), the second is to a manual containing 8,519
records (cap: 11411).
 ...
Effort is underway to archive some more of this data but will not be
happening immediately. Has anybody experienced had any similar
experiences, or have any insight to offer?
>>
 
This auto master is *way* too full-almost 90% full. With this many
records, secondaries get really expensive. Expand the auto master such
that it's no more than 70% full, which would be to at least 7.15 million
records, and you should see a significant improvement in throughput.
 
Steve Dirickson         WestWin Consulting
(360) 598-6111  [log in to unmask]