From a seminar at IBM in San Jose that was specifically on the issue of
Performance and trouble shooting, a database between 12GB and 17GB
(considered 'max' size) is the point at which the ADSM server needs to
be split.  From the experience of those on the list where AUDIT or
SELECT and especially DUMPDB, LOADDB, AUDITDB this cap on database size
really does seem to be appropriate.

Steffan

"Mauro M. TINELLI" wrote:
>
> John,
>
> my 2 cents ... I have a 25GB DB which is 50% full, I had before a 9GB DB.
> I erroneously supposed to Audit-DB it. With the previous one I managed to
> do it a couple of time, now after 26 hours and 135.000.000 entries, I
> decided that I'm using a huge DB and I interrupted the operation at my
> own risk!
>
> My daily backup is 45 mins, it'll be 1:30 hours if it was full ... I
> guess you are well over 2 hours.
>
> So my conclusion is that 40 GB is big enough to be considered HUGE by
> ADSM standard.
>
> Thank you
>
> Mauro, STM
>
> > Richard Sims responded:
> > >  The consensus is that when your server
> > > reaches "huge" size that you subdivide into multiple servers.
> >
> > Thanks for the response.  When I do a Q DB, I get:
> > ANR5965I Console command:  Q DB
> >
> >
> >
> > Available Assigned   Maximum   Maximum    Page     Total      Used
> Pct
> > Max.
> >     Space Capacity Extension Reduction    Size    Usable     Pages
> Util
> > Pct
> >      (MB)     (MB)      (MB)      (MB) (bytes)     Pages
> > Util
> > --------- -------- --------- --------- ------- --------- ---------
> -----
> > -----
> >    36,764   36,764         0     4,988   4,096 9,411,584 7,912,982
> 84.1
> > 84.1
> >
> >
> > adsm>
> >
> >
> > The DataBase is at 36.7GB.  Is this "huge"?
> >
> > John G. Talafous                         Sr. Tech. Prog/Anal
> > The Timken Company                 Phone: (330)-471-3390
> > P.O. Box 6927                           Fax  : (330)-471-4034
> > 1835 Dueber Ave. S.W.
> > Canton, Ohio USA  44706-0927
> > talafous AT timken DOT com                  http://www.timken.com/