From: "Jonathan Lewis" Newsgroups: comp.databases.oracle.server Subject: Re: Extent Allocation among Multiple Datafiles ? Date: Sat, 9 Sep 2000 18:39:25 +0100 Message-ID: <968521406.12173.0.nnrp-08.9e984b29@news.demon.co.uk> References: <8p7207$9rf$1@nnrp1.deja.com> <968314038.14856.0.nnrp-03.9e984b29@news.demon.co.uk> <8p9l20$bha$1@nnrp1.deja.com> <968435216.19084.0.nnrp-12.9e984b29@news.demon.co.uk> NNTP-Posting-Host: jlcomp.demon.co.uk X-NNTP-Posting-Host: jlcomp.demon.co.uk:158.152.75.41 X-Trace: news.demon.co.uk 968521406 nnrp-08:12173 NO-IDENT jlcomp.demon.co.uk:158.152.75.41 X-Complaints-To: abuse@demon.net X-Newsreader: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Lines: 39 I've just run a few tests of this with locally managed tablespaces, usng the 'alter table allocate extent' command, and the algorithm certainly seems to be a round-robin. I vaguely recall seeing something in the manuals to this effect too, but can't find it at present (isn't that always the way). There is no visible clue in the recursive activity to prove that Oracle is doing a round-robin, other than the fact that Oracle loads the file$ details for all the files in the tablespace as the first step of allocating the extent. Presumably the actual decision code is hidden in dictionary cache processing of dc_used_extents. -- Jonathan Lewis Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk Jonathan Lewis wrote in message <968435216.19084.0.nnrp-12.9e984b29@news.demon.co.uk>... > >It's just occurred to me that the apparent round-robin >may be a side-effect of the way space management >works on dictionary managed tablespaces and not >a planned feature. I'm going to have a proper look at >it, and will get back to you. > >-- > >Jonathan Lewis >Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk > > >