Author: "Burton, Robert" <ROBERT.BURTON AT ROYALBANK DOT COM>
Date: Tue, 1 Feb 2000 10:57:01 -0500
We have a 23,576 MB database, that originally was running at 94% utilised. By moving clients to other servers and deleting filespace we have reduced our capacity to 37.3%. We are trying to reclaim so
Author: Andreas Buser <andreas.buser AT BASLER DOT CH>
Date: Tue, 1 Feb 2000 17:26:33 +0100
Hi Robert, yes there is a way. 1. reduce your DB (Properties of DB in GUI under FILE) by the amount you want. 2. remove one or more DB-Volumes ( so your database gest smaller) If you have your whole
Author: "Bates, Richard" <Richard.Bates AT VERTEX.CO DOT UK>
Date: Tue, 01 Feb 2000 11:22:40 -0500
Robert, I can't remember where I found this info (list or manual) but here goes: "The ADSM Server database has a b-tree organisation with internal references to index nodes and siblings. The database
Author: Herve Chibois <Herve.Chibois AT FR.ABNAMRO DOT COM>
Date: Tue, 1 Feb 2000 17:32:48 +0100
Hi Robert, If the field 'Maximum Reduction is greater than a DB volume, ou can reduce the db and delete the db volume and ADSM will move the data onto another volume. Herve For instance, I can only r
The tsm 3.7 server has improved dumpdb, loaddb facilities which should do a reorg in a reasonable amount of time while actually doing some good. The b-tree splitting is done in a manner that makes th