Hi Eric,

Can you provide the output of q dbvol f=d ?

 
 

Regards,

David le Blanc

--              
Senior Technical Specialist             
I d e n t i t y   S o l u t i o n s     
        
Level 1, 548 Bridge Road, Richmond, Vic 3121
Ph 03 8420 3420 Fax 03 8420 3440 Mobile 0417 595 550
Email [EMAIL PROTECTED] 
 

> -----Original Message-----
> From: Eric Winters [mailto:[EMAIL PROTECTED] 
> Sent: Friday, 9 December 2005 2:21 PM
> To: [email protected]
> Subject: [ADSM-L] Deleting TSM db volumes in lightly utilized db
> 
> Dear All,
> 
> Cannot seem to find a way to delete db volumes in a lightly 
> used TSM db.
> 
> Environment is as follows;
> 
> TSM Server 5.3 on Windows.
> 
> q db
> 
> Available   Assigned     Maximum     Maximum      Page       Total
> Used         Pct            Max.
>     Space    Capacity   Extension        Reduction      Size  
>        Usable
> Pages       Util           Pct
>      (MB)       (MB)           (MB)                  (MB)
> (bytes)      Pages                                            Util
> ---------   --------   ---------   ---------               -------
> ---------     ---------           -----            -----
>    81,000     74,684       6,316                    0
> 4,096        19,119,104   6,606,896    34.6    34.6
> 
> I have 8x10,000 MB dbvolumes - I'd like to reduce this to 
> perhaps 4x10,000
> MB volumes.
> When running "delete dbvolume" I get the following (expected) message
> ANR2434E DELETE DBVOLUME: Insufficient space on other 
> database volumes to
> delete volume D:\path\to\dbvolume
> ANS8001I Return code 7.
> 
> Now I understand from Richard's excellent Quickfacts that db 
> volumes can
> become fragmented - and that the 'maximum extension' refers 
> to contiguous
> space at the end of the db - which needs to  be large enough 
> to accommodate
> the data deleted from dbvolumes.  To create a larger 'maximum 
> extension'
> I've defined additonal 20 GB of dbvolumes - but after 
> deleting 2x10,000 db
> volumes with data on them I find the 'maximum extension' has 
> dropped by
> exactly 20,000 - so I haven't actually reduced my total db 
> size at all. I
> had naively hoped that the effect of deleting db volumes and 
> forcing that
> data onto other volumes would have defragemented the data on 
> that volume.
> 
> So what are my alternatives? I really don't want to unload 
> this db and I
> doubt defragmentation be achieved via a db backup/restore. Is there a
> better way?
> 
> Thanks for your suggestions people.
> 
> Regards,
> 
> Eric Winters
> Sydney
> Australia
> 

Reply via email to