>Anyone who depends on data from volumeusage might consider opening a
>problem with IBM/Tivoli. Really bad performance can be reported and will sometimes
>be fixed instead of getting the dread 'working as designed' response.
>I have always used occupancy data to make reports. In version 1
>it wa
I have never been able to do a simple 'select * from volumeusage'. It will always
hang the server which is 3.7.3.8 on os/390 r6. I think the problem compared to
other tables is that volumeusage may not be a real table in the database.
Instead I think it is really just a select on the contents ta
I am still on ADSM 3.1 with OS/390. I have found variants of this query
impossible to
run during normal hours, when other users (online business) seem to think
they are
more important than mere housekeeping functions.
Running out of hours, my query (select node_name from volumeusage where
stgpoo
the period.
John
Mark Brown <[EMAIL PROTECTED]> on 11/02/2000 04:31:34 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject: Re: Really bad performance for a sql query after upgrading to v 3
Mark - Offhand I don't see any APARs relating to your SQL query, so maybe
you can isolate what the problem might be by using a spectral
approach, doing selects from simple "select * from volumeusage", with
increasing complexity through to your problem select statement.
It may be the Group B
To answer your questions, adsm database is as follows:
Available Assigned Maximum MaximumPage Total Used
Pct Max.
Space Capacity Extension ReductionSizeUsable Pages
Util Pct
(MB) (MB) (MB) (MB) (bytes)
Pages Util
- --
Mark,
Couple of suggestions.
1) How full is your database, sql queries use free space in the database as a
work area.
2) Run as a batch job, then you can just cancel the session if it is using too
much resource, and or taking too long.
Mark Brown <[EMAIL PROTECTED]> on 11/02/2000 02:45:05 PM
