I should have said the max for DB and LOgs. I got this information,
thanks..
>From http://people.bu.edu/rbs/ADSM.QuickFacts :
Database, maximum size Per APAR IC15376,
the ADSM database
should not
exceed 500 GB.
Per the TSM
5.1 Admin Guide: 530 GB.
Ref: Server
Admin Guide, topic
Increasing
the Size of the Database or
Recovery Log
topic, in Notes.
See: SHow
LVMFA, which reveals that the
max is
actually 531.2 GB. (See the
reported
"Maximum possible DB LP Table
size".)
Recovery log, maximum size Per APAR IC15376, the
recovery log
should not
exceed 5.5 GB (5440 MB). But
APAR IY09200
says that the maximum size
is 5420 MB;
and the max usable is 5416
MB (because of
how calculations are
performed
which store data structures in
a certain
fixed area in the first 1 MB
of each DB and
LOG volume).
Msgs: ANR2452E
and ANR2429E
Ref: Server
Admin Guide, topic
Increasing
the Size of Database or
Recovery Log
topic, in Notes.
See: SHow
LVMFA, which reveals that the
max is 5.3GB,
not 5.5. (See the reported
"Maximum
possible LOG 1 LP Table size".)
As of TSM 4.2
(June 2001), the maximum
size of the
recovery log is increased to
13 GB. (Note
that automatic expansion of
the database,
by DBBackuptrigger, will
not go beyond
12 GB.)
Advisory: It
is best to not run with a
maximum value
because you may run into
the very ugly
ANR7837S situation where
your Recovery
Log is full and, being at
the maximum,
you can't add space to get
your server
restarted. And consider
running in
Normal rather than
Rollforward
mode: many customers are
doing that to
avoid log filling
problems.
Respectfully,
Victoria
"Make Peace with Imperfection"
|
