Xref: alice comp.databases.oracle.server:47906 Path: alice!news-feed.fnsi.net!newspump.monmouth.com!newspeer.monmouth.com!dispose.news.demon.net!demon!news.demon.co.uk!demon!jlcomp.demon.co.uk!not-for-mail From: "Jonathan Lewis" Newsgroups: comp.databases.oracle.server Subject: Re: Direct LOAD - UNRECOVERABLLE - Question Date: Fri, 30 Apr 1999 23:04:52 +0100 Message-ID: <925510027.15294.0.nnrp-80.294b989e@news.demon.co.uk> References: <7gcefl$bjb$1@cronkite.ocis.temple.edu> <1396.789T649T12292928lothar.armbruester@rheingau.netsurf.de> X-Trace: news.demon.co.uk 925510027 nnrp-80:15294 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: 25 Absolutely right. After a direct load, SQL*Load creates a 'mini' index on the new data, then merges it with the old data by copying. So temporarily the tablespace needs to be able to hold two complete copies of the index. As you say, if there isn't enough space, the copy/merge fails and the index stays in Direct Load state. -- Jonathan Lewis Yet another Oracle-related web site: www.jlcomp.demon.co.uk Lothar Armbrüster wrote in message <1396.789T649T12292928lothar.armbruester@rheingau.netsurf.de>... > >I have observed that the loader need huge amounts of tablespace when >rebuilding the indexes. If the free space does not suffice, recreating the >indexes after the load may use much less tablespace. >