Actually, to remove a volume from a database, you have to reduce the
database first, using the REDUCE DB command, and then delete the
database volume.  You cannot reduce your database because there are
database pages in every partition for your database (e.g. every 4MB
piece).  The fact that you cannot reduce your database is displayed in
the QUERY DB command under the column named Maximum Reduction.

Mike Kaczmarski




Steven P. Roder writes:
 > On Tue, 28 Jan 1997, Jeff Robbins wrote:
 > > I am trying to shrink the size of my ADSM database and am finding it
 > > very difficult.  Why is it that I can not reduce my database with
 > > the following numbers:
 > >
 > > Available Assigned   Maximum   Maximum    Page     Total      Used %Util  
 > > Max.
 > >     Space Capacity Extension Reduction    Size    Usable     Pages       
 > > %Util
 > >      (MB)     (MB)      (MB)      (MB) (bytes)     Pages
 > > --------- -------- --------- --------- ------- --------- --------- ----- 
 > > -----
 > >     5,172    4,992       180         0   4,096 1,277,952   972,907  76.1  
 > > 78.0
 > >
 > > my server is at the following:
 > > ADSM Server for VM - Version 1, Release 1, Level 0.16/1.16
 > >
 >
 > What does "q dbv" return?  In order to reduce the database, you have to
 > delete a database volume, and the data in that volume has to fit on the
 > other remaining volumes.  Additionally, the increment that can be deleted
 > depends on the sizings of the VM Minidisks that hold the data.  You cannot
 > delete part of a minidisk.
 >
 > It may be that you will have to define more space in order to remove any,
 > so that ADSM can migrate off of the minidisk (dbvolume) that you want
 > removed.
 >
 > Hope this helps,
 >
 > Steve (unVMix Systems Programmer/Dude) Roder
 > (tkssteve AT ubvm.cc.buffalo DOT edu | tkssteve AT acsu.buffalo DOT edu | 
 > (716)645-3564 ,
 >    | http://ubvm.cc.buffalo.edu/~tkssteve)