From oracle-l-bounce@freelists.org Tue Apr 26 13:33:33 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j3QIXXs0020610 for ; Tue, 26 Apr 2005 13:33:33 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j3QIXV4Z020602 for ; Tue, 26 Apr 2005 13:33:32 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 40AEA186AE7; Tue, 26 Apr 2005 12:31:05 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12132-06; Tue, 26 Apr 2005 12:31:05 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id B2F8A186A69; Tue, 26 Apr 2005 12:31:04 -0500 (EST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Tue, 26 Apr 2005 11:28:52 -0600 Subject: Re: LOCALLY MANAGED EXTENT PERFORMANCE From: Tim Gorman To: Oracle-L Message-ID: In-Reply-To: <10644b9e05042515044abdbed9@mail.gmail.com> Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-archive-position: 19035 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: tim@evdbt.com Precedence: normal Reply-To: tim@evdbt.com X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on air891.startdedicated.com X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=ham version=2.63 >> Doesn't do the job. This only tells me what the largest extent sizes are >> for segments. It does not tell me whether any of them are possible to run >> out of space within "N" extensions... > > Assuming autoextention on the datafiles, why are you worrying about > how many extents until you run out of disk space? It seems to me that > it now makes more sense to keep on eye on disk space itself. Unless > you are trying to run your mountpoints to 99% full or you have small > mountpoints, ask the sysadmins to set a warning at X% and an alarm at > Y%. Autoextension can *postpone* the need for this kind of monitoring, but does not eliminate it. Think it through. It's not a good idea to assume autoextension (or even extensibility) in all scenarios, whether at the datafile level or at the file-system level. -- http://www.freelists.org/webpage/oracle-l