>I noticed that after awhile, my database gets quite large. Assuming that
>it's consistent, unloaddb/loaddb seems to compress out all of the junk and
>makes it much smaller. Is there a way to check the database for how much
>space might be recovered by doing an unloaddb/loaddb? Currently, I'm at
>about 100GB.
A frequently asked question. There is no "junk" in the database. What you
are achieving, at the expense of downtime and some jeopardy, is a short-lived
compaction of the data in the database. Reasonable Policy definitions,
expiration, and disposal of obsolete filespaces is the ultimate salvation for
a TSM database. Don't get into the habit of doing unloaddb/loaddb. As the
expression goes, "It's a database...".
Richard Sims, BU
|