Filespace deletion removes both active and inactive versions thus removing
more entries than expiration in the DB.
Zlatko Krastev
IT Consultant
"Stapleton, Mark" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09.03.2003 23:21
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: unload/reload db on diff.server (same library) -- disaster
waiting to
happen?
From: Adam J. Boyer [mailto:[EMAIL PROTECTED]
> Due to some misunderstanding, an unnecessary 5 million files
> was backed up, bloating our database by about 15 GB. I have
> since commenced deleting that filespace, but it looks like
> the delete is not reducing the database size nearly enough.
> So I am planning to do an unload/reload, and in order to
> eliminate downtime,
<snip>
> The only downside I can think of is that after the
> reorganized database is restored to the production server,
> all transactions made during the
> unload/reload will be lost.
Don't do it. You'll be spending months fixing it, and it'll never get
fixed. (Besides, an unload/load of the db won't get you what you want.)
What command did you use to delete the filespace? Did you run an
expiration after the deletion?
--
Mark Stapleton ([EMAIL PROTECTED])
