Joachim, Not sure where to look further. I do think your cache hit rate is a bit low. My database statistics show Available Space (MB): 27,936 Assigned Capacity (MB): 27,936 Maximum Extension (MB): 0 Maximum Reduction (MB): 3,064 Page Size (bytes): 4,096 Total Usable Pages: 7,151,616 Used Pages: 5,453,023 Pct Util: 76.2 Max. Pct Util: 77.1 Physical Volumes: 24 Buffer Pool Pages: 12,288 Total Buffer Requests: 112,683,745 Cache Hit Pct.: 99.06 This was after running expiration in 4 hours 50 minutes which deleted q uite a lot of objests ANR0812I Inventory file expiration process 3 completed: examined 3750451 objects, deleting 415022 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were encountered. My region size is 768 mb. but my bufferpool is only half as big with a larger database. There was a thread about bufferpool and region sizes a while ago, which might be worth looking at.
Schaub Joachim Paul ABX-SECE-ZH <[EMAIL PROTECTED]>@vm.marist.edu> on 10/29/2003 11:54:30 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: AW: AW: AW: delete filespace takes >24hours yes on this TSM server runs the expire about 5 hours, the database should have enough space q db f=d: Available Space (MB): 20,784 Assigned Capacity (MB): 20,784 Maximum Extension (MB): 0 Maximum Reduction (MB): 3,644 Page Size (bytes): 4,096 Total Usable Pages: 5,320,704 Used Pages: 3,536,071 Pct Util: 66.5 Max. Pct Util: 67.1 Physical Volumes: 34 Buffer Pool Pages: 24,576 Total Buffer Requests: 349,306,341 Cache Hit Pct.: 98.03 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 1,119.86 Percentage Changed: 8.11 Last Complete Backup Date/Time: 28.10.2003 16:08:19 thank you and regards joachim -----Ursprüngliche Nachricht----- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 12:42 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: delete filespace takes >24hours Just trying a few ideas. An ok expiration performance is one that you are happy with, so would be a lot less than 24 hours (say under 4 hours) The discard data with the volumes was just a thought, that maybe your database was nearly full, so did not have enough free space to build up the table for the full 160,000 delete You did not provide database statistics Schaub Joachim Paul ABX-SECE-ZH <[EMAIL PROTECTED]>@vm.marist.edu> on 10/29/2003 10:54:02 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: AW: AW: delete filespace takes >24hours what means an o.k. expiration performance? why should it go faster to delete volumes(in 3 pools)? thanks joachim -----Ursprüngliche Nachricht----- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 11:21 An: [EMAIL PROTECTED] Betreff: Re: AW: delete filespace takes >24hours Is your expiration performance ok. Do you know how many tapes this client has. Maybe it would go faster with delete volume discarddata Schaub Joachim Paul ABX-SECE-ZH <[EMAIL PROTECTED]>@vm.marist.edu> on 10/29/2003 09:31:25 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: AW: delete filespace takes >24hours some weeks ago we had memory problems, so the system is 'IBM checked' now. No Resource Problem (800mb Regionsize, DB Bufferpool near 100MB), Cache Hit Ratio is > 98.5% ! -----Ursprüngliche Nachricht----- Von: John Naylor [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 29. Oktober 2003 10:11 An: [EMAIL PROTECTED] Betreff: Re: delete filespace takes >24hours Joachim, I am on os390 2.10 expecting to go z/os shortly and I would expect that size of filespace to be deleted in an hour or so. What does your DB cache hit rate show. If you have any sort of performance monitor such as RMF, I would take a look at that to see if it thinks TSM is short of resource. John Schaub Joachim Paul ABX-SECE-ZH <[EMAIL PROTECTED]>@vm.marist.edu> on 10/29/2003 08:52:53 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: delete filespace takes >24hours Dear *SM Group I have to delete filespaces. One of the delete process runs longer 24 hours. the FI is apr. 150GB and 160000 Files in size. How work the TSM DB? One select, one commit, one select one commit? If i would create an sql select on an Oracle DB it would take a few second to delete the entries! Environment: TSM Server 5.1.5.4 on Z/OS 1.3, enough memory, cpu, cache hit etc. Regards Joachim ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 Internet: http://www.abraxas.ch ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 5 Jahre Abraxas - Ein grosser Erfolg ! http://www.abraxas.ch/top_Downloads/abxnews/jubi_news.pdf ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ********************************************************************** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **********************************************************************