I would try doing a full DB backup. Can you send "q dbv" output too?

[RC] 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Tuesday, December 02, 2008 9:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Where is the missing 38GB?

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".


DISCLAIMER:
This message is intended for the sole use of the addressee, and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If you are not the addressee you are hereby notified that you 
may not use, copy, disclose, or distribute to anyone the message or any 
information contained in the message. If you have received this message in 
error, please immediately advise the sender by reply email and delete this 
message.