Shoot me if I am wrong, but isn't this a correct result? The database uses 0,001 times the assigned capacity, that is around 50 Megabytes. Of these 50 Megabytes, zero MB is recoverable by a dbreorg. As of my knowledge "estimate dbreorg" operates on how much is actually utilized.
So if you dump it and load it, it will consume the space(Pct.util times Assigned Capacity/100) minus the estimated recoverable space. The db will then fit onto something a little bigger than a 50 MB volume.(the output from the dump will tell you how much is needed). Sounds reasonable to me. Hans Chr. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Wednesday, December 03, 2008 3:09 PM To: [email protected] Subject: Re: Where is the missing 38GB? 9:08:28 AM TSMTEST : q db f=d Available Space (MB): 56,336 Assigned Capacity (MB): 53,264 Maximum Extension (MB): 3,072 Maximum Reduction (MB): 14,360 Page Size (bytes): 4,096 Total Usable Pages: 13,635,584 Used Pages: 15,780 Pct Util: 0.1 Max. Pct Util: 0.1 Physical Volumes: 6 Buffer Pool Pages: 131,072 Total Buffer Requests: 69,643 Cache Hit Pct.: 80.90 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 0.38 Percentage Changed: 0.62 Last Complete Backup Date/Time: 12/02/2008 13:54:50 Estimate of Recoverable Space (MB): 0 Last Estimate of Recoverable Space (MB): 12/02/2008 12:41:54 "Conway, Timothy" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> 12/02/2008 05:43 PM Please respond to "ADSM: Dist Stor Manager" <[email protected]> To [email protected] cc Subject Re: [ADSM-L] Where is the missing 38GB? How about a q db f=d now that the estimate dbreorgstats is finished? The "q dbv f=d" doesn't really give anything that's affected by the estimate. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Remco Post Sent: Tuesday, December 02, 2008 3:04 PM To: [email protected] Subject: Re: [ADSM-L] Where is the missing 38GB? Ok, this is an almost empty database with a lot of fragmentation. I'd say, from what I read in the thread, that an unload/load at this point will remove a lot of fragmentation, even though the estimate says nill. The other option is to run an export server, reformat everything, and then import server. You'll probably want to save your devconf.txt so you can easily recreate the stgpools, devclasses and server2server comms you might have. On Dec 2, 2008, at 18:20 , Zoltan Forray/AC/VCU wrote: > I have a test TSM server (5.5.1) which is producing some strange DB > statistics. > > ************************************************** > *** ---> Q DB F=D > ************************************************** > > > Available Space (MB): 56,336 > Assigned Capacity (MB): 53,264 > Maximum Extension (MB): 3,072 > Maximum Reduction (MB): 14,360 > Page Size (bytes): 4,096 > Total Usable Pages: 13,635,584 > Used Pages: 15,676 > Pct Util: 0.1 > Max. Pct Util: 0.1 > Physical Volumes: 6 > Buffer Pool Pages: 131,072 > Total Buffer Requests: 249 > Cache Hit Pct.: 100.00 > Cache Wait Pct.: 0.00 > Backup in Progress?: No > Type of Backup In Progress: > Incrementals Since Last Full: 4 > Changed Since Last Backup (MB): 211.15 > Percentage Changed: 344.82 > Last Complete Backup Date/Time: 08/20/2008 09:49:38 > Estimate of Recoverable Space (MB): > Last Estimate of Recoverable Space (MB): > > > With an assigned capacity of 52GB yet only 0.1% utilized (52MB?), it > says I can only reduce the DB by 13GB ???? > > So, where is the remaining 38GB of DB usage ? > > There are 5-Disk STG volumes (empty/0% utilized), 2-Nodes with NO > filespaces, defined. "Q STG" shows: > > 12:15:11 PM TSMTEST : q stg > > Storage Device Estimated Pct Pct High Low Next > Stora- > Pool Name Class Name Capacity Util Migr Mig Mig ge Pool > Pct Pct > ----------- ---------- ---------- ----- ----- ---- --- > ----------- > ARCHIVEPOOL DISK 0.0 M 0.0 0.0 90 30 > BACKUPPOOL DISK 123 G 0.0 0.0 90 30 > COPYPOOL-I- IBM3583-1 0.0 M 0.0 > BM3583-1 > COPYPOOL-I- IBM3583-2 0.0 M 0.0 > BM3583-2 > IBM3494-35- 3592E05 0.0 M 0.0 0.0 90 70 > 92 > > I did a "DSMSERV AUDITDB FIX=YES" and the only thing it complained > (and > fixed) about was old schedules for non-existing nodes. Also did an > "EXPIRE INVENTORY". -- Met vriendelijke groeten, Remco Post [EMAIL PROTECTED] +31 6 248 21 622 This email originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO, http://www.steria.no. This email and any attachments may contain confidential/intellectual property/copyright information and is only for the use of the addressee(s). You are prohibited from copying, forwarding, disclosing, saving or otherwise using it in any way if you are not the addressee(s) or responsible for delivery. If you receive this email by mistake, please advise the sender and cancel it immediately. Steria may monitor the content of emails within its network to ensure compliance with its policies and procedures. Any email is susceptible to alteration and its integrity cannot be assured. Steria shall not be liable if the message is altered, modified, falsified, or even edited.
