RE: Finding reason for high temp storage maximum

How often are the jobs using ODBC/JDBC doing commits?  Could be your
temp storage is due to DB changes remaining in cache.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of ouuch@xxxxxxxxxxx
Sent: Thursday, December 04, 2003 9:57 AM
To: Midrange Systems Technical Discussion
Subject: Re: Finding reason for high temp storage maximum


On 4 Dec 2003 at 10:14, Vern Hamberg wrote:

> Oliver
> 
> Our disk/HUNTER product has a command with which you can get a
snapshot of 
> the top 20 jobs by temporary storage.

It is not so much a question of finding the culprit jobs (mostly, index
builds are also
consuming lots of CPU), but catching the temp storage growth before it
hits our ASP1
threshold (at 90%). 

Beyond SNADS, what else will be shut off when the threshold fires?

Regards,

Oliver
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.