On a system with 677 mail files totalling around 170gb we ran DBSCAN, 
manually.  After 4 days of running we bounced the server for other 
business reasons.  Of course this aborted the scan.

Any way to tune that bad boy to finish in a more timely fashion?

This system is dedicated to domino.  As long as other domino processes run 
I do not care about other interactive and batch processes.  The number of 
iSeries userid's is very limited.  Strictly operations personnel.  There 
are no 'traditional' batch jobs.  Backup is only done once a week, 
dedicated, from the system console.  (It's a cluster backup machine.)

Resource        Type-model
CEC01            9406-270 
PN01             247D 
MP01             25BD-000 
MP02             25BD-000 
PV01             2454-001 

Sys      Pool   Reserved    Max  ----DB-----  --Non-DB---  Act-   Wait- 
Act- 
Pool    Size M   Size M     Act  Fault Pages  Fault Pages  Wait   Inel 
Inel 
  1     191.27    106.29  +++++     .0    .0    8.0   8.8   13.1     .0  
.0
  2    2656.01      7.05    838    1.6   3.6  157.2 350.9   4860     .0  
.0
  3     149.86       .00     58     .0    .0     .2    .3    1.0     .0  
.0
  4        .25       .00      1     .0    .0     .0    .0     .0     .0  
.0
(scan not running at this time)

Controlling subsystem  . . . :   QBASE

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].