Re: Changed SQL behavior under server 6.2.3.1

2015-01-09 Thread Schofield, Neil (Storage Middleware, Backup Restore)
David Thanks for the suggestion. I would have thought both were equivalent, but I tried each of them anyway and both gave the wrong answer: tsm: Xselect count(*) from nodes where node_name not in (select node_name from filespaces) Unnamed[1] 0 tsm: Xselect

Re: Changed SQL behavior under server 6.2.3.1

2015-01-09 Thread Prather, Wanda
Oooh, that's evil. Had a consult with the in-house DBA. This works for me on V7.1.1: select count(*) from nodes where node_name not in (select node_name from filespaces where node_name is not null) In V6-7 there is 1 filespace with a NULL node name - looks to me like something created by

Re: SAN hardware hints

2015-01-09 Thread Rhodes, Richard L.
Yes, Win 2008 R2. And they have EMC PowerPath multipathing sftw. The issue with charge back is kind of tricky. When we talk with a vendor they always tell us there is absolutely no way we _shouldn't_ be using thin devices, reguardless of chargeback. So we then ask . . . How? We

DB2 LOCKLIST parameter

2015-01-09 Thread Thomas Denier
Inventory expiration processes on one of our TSM servers have been failing occasionally with no obvious explanation. We were able to get trace data for the most recent failure. IBM reviewed the trace data and advised us to increase the DB2 LOCKLIST parameter. They referred us to a technote at

Re: Changed SQL behavior under server 6.2.3.1

2015-01-09 Thread Schofield, Neil (Storage Middleware, Backup Restore)
Zoltan Thanks for the response. I'm not sure whether this is platform related - all my tests were conducted on servers running on AIX. While the problem is not apparent on v5.x instances, it seems to affect v6.x instances at all our levels. Like Margaret's experience back in 2012, the problem

Re: SAN hardware hints

2015-01-09 Thread Vandeventer, Harold [OITS]
Thanks for a long reply I manage our TSM environment but also SAN space. Your comments about charge back, performance stats, and support will be helpful there too. Re the microcode updates: are you Win boxes 2008 or 2008 R2? -Original Message- From: ADSM: Dist Stor Manager

Re: Changed SQL behavior under server 6.2.3.1

2015-01-09 Thread RIGAUDIERE, David
Hi, the last query should be select count(*) from nodes where node_name not in (select node_name from filespaces) NOT keyword between column name and IN keyword. David RIGAUDIERE Prestataire Logic SI2M - Direction des Systèmes d’Information Groupe Malakoff Médéric Direction de la Production

Re: SAN hardware hints

2015-01-09 Thread Rhodes, Richard L.
We use EMC storage. Most of our TSM databases and disk pools are on VNX/VNX2. In general we like them, especially since they came out with the VNX2 - they finally have enough processor power to drive the array. We use all fat luns. We have a charge back system for storage and thin

Re: Size of restore

2015-01-09 Thread Erwann SIMON
Hello, Lets try : dsmc query backup /your folder/ -subdir=yes -querysummary The -querysummary flag is available beginning with TSM 6.1 B/A Client. -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: Hans Christian Riksheim bull...@gmail.com À:

Re: Size of restore

2015-01-09 Thread Rejean Larivee
Hello, I believe what you are looking for is the -querysummary client option. You would use that with the query backup command. For example : dsmc query backup d:\foldertorestore\* -su=yes -querysummary Look for the Summary Statistics at the end of the output. Rejean Larivee IBM Tivoli Storage

Size of restore

2015-01-09 Thread Hans Christian Riksheim
A user has deleted a folder. How can I quickly get an indication or a number on how much data and how many files will be restored so I can provide a guesstimate of the restore time? I can't remember exactly but I think there was a function for that in the earlier versions of the BA GUI .

Re: Changed SQL behavior under server 6.2.3.1

2015-01-09 Thread Zoltan Forray
What is your platform/OS? I recently upgraded from 6.3.4.300 to 6.3.5.100 and am seeing lots of problems with selects not return consistent/correct results as their non-select counterparts. The reason I ask about the OS is IBM has stated there are known problems with RedHat 6 kernels causing

Re: Changed SQL behavior under server 6.2.3.1

2015-01-09 Thread Schofield, Neil (Storage Middleware, Backup Restore)
I've just tried the select statement on v6.3.5.0 that Margaret tried below in 2012 and it still returns no rows. Does anyone have a work-around that can be used? Regards Neil On 6/21/2012 9:55 AM, Clark, Margaret wrote: Using TSM server 6.2.3.1, the following SQL command no longer works: