Re: Finding reason for high temp storage maximum -- MIDRANGE-L

Subject: Re: Finding reason for high temp storage maximum
From: ouuch@xxxxxxxxxxx
Date: Thu, 04 Dec 2003 18:56:41 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>
Priority: normal

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Finding reason for high temp storage maximum , Mark Allen
Re: Finding reason for high temp storage maximum , Vern Hamberg

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.