Andy, I do not see an error in your SQL statement, but the results are much too good to be correct, new volumes must be created on the fly during the SQL run: e.G. AOHEXCHANGE00 TPBACSAFE 81 While I
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Fri, 2 May 2003 07:18:18 -0700
What do you get if you do this: select stgpool_name, volume_name from volumeusage where node_name='AOHEXCHANGE00' order by stgpool_name, volume_name Are duplicate volumes showing up? How about: selec
Or how about this one, it's what we use. It is a large query and takes a while to complete depending on the size of your TSM server. select node_name,stgpool_name,count(distinct(volume_name)) as \"Nu
Author: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
Date: Fri, 2 May 2003 10:37:04 -0400
Try replacing count(*) as "Count" with count(distinct volume_name) as "Count" The problem is that a volser can appear multiple times in volumeusage for a given node/storagepool combination. David And
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Fri, 2 May 2003 08:43:05 -0700
Ah yes, you are correct, since file spaces and copy type are part of the volume usage table. Thanks! Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-ma