It can't hurt! If you don't need to run it, it will complete fairly
quickly without doing anything. If you do need it, it will toil away and
do its job. I was surprised at how much it cleaned up - my database went
from 92% full to 79% full. Run it on a weekend - it is fairly compute
intensive if it does some actual good.

If you run it, and it does actual work, watch out for a Log fillup! If
you don't already have 12gb of log space, you might want to temporarily
add a log volume to make it 12GB before running CLEANUP BACKUPGROUPS.
(Why 12GB? The max is 13GB. You always want to leave some room under the
13GB limit so that if it does actually fill up, you can rescue yourself
by adding the last GB. If you fill up the entire 13GB limit, you'll be
really badly stuck.) If it threatens to fill the log, you can cancel the
CLEANUP BACKUPGROUPS process, run a database backup to empty the log,
and restart CLEANUP BACKUPGROUPS.

(Yes, I had a full-log-crash during CLEANUP BACKUPGROUPS. I am NOT
running LOGMODE ROLLFORWARD.)

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu


On Tue, 20 Jan 2004, Helen Tam wrote:

>Hi,
>    Do you still need to run 'cleanup backupgroups' utility if there is
>Window clients?
>                                                               Thanks, Helen
>
>At 10:18 AM 1/19/2004 +0100, you wrote:
>>Yes, that's true. They changed something in the database.
>>Mostly the upgradedb-command is issued automaticly when you install
>>the package. Otherwise run it manually
>>
>>
>>
>> >>> manattha.tops AT CRCAHOLD.CO DOT TH 19/01 4:55  >>>
>>Dear all
>>            i just upgrade TSM 4.1.0 to 5.1.5.0. I have some question
>>            I shuold run command "DBUPGRADE". It's right ?Pls answer me
>>            Thank you
>>
>>Natthakriss  Mathanom
>>MIS System Operations
>>CRC.Ahold Company Limited
>>Tel    : 662-9371700 ext 833
>>Email : manattha.tops AT crcahold.co DOT th
>