Path: news.easynews.com!core-easynews!newsfeed3.easynews.com!easynews.com!easynews!news.glorb.com!sn-xit-02!sn-xit-04!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: Sybrand Bakker Newsgroups: comp.databases.oracle.server Subject: Re: Extent Management 101 Date: Sun, 08 Aug 2004 22:27:01 +0200 Organization: Posted via Supernews, http://www.supernews.com Message-ID: Reply-To: postbus@sybrandb.verwijderdit.demon.nl References: <91721cf.0408080703.1d50b088@posting.google.com> X-Newsreader: Forte Agent 2.0/32.652 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@supernews.com Lines: 24 Xref: core-easynews comp.databases.oracle.server:227818 X-Received-Date: Sun, 08 Aug 2004 13:29:27 MST (news.easynews.com) On 8 Aug 2004 08:03:47 -0700, melliott42@yahoo.com (Michael) wrote: >Hello, > >Though I have read about Extents in various books, as a new Oracle DBA >using 8.17 I still do not grasp how I need to manage them. > >1. Basically, what are common Extent related issues and what are the >actions as a DBA I need to know to address them? > >2. Any absolute Do's and Dont's on managing Extents? > > >Thanks for your advice, > >Michael just make sure all your tablespaces except System are locally managed and forget about the issue. -- Sybrand Bakker, Senior Oracle DBA