Xref: alice comp.databases.oracle.server:47182
Path: alice!news-feed.fnsi.net!netnews.com!feed1.news.rcn.net!rcn!newsfeed.cwix.com!192.232.20.2!malgudi.oar.net!plonk.apk.net!news.apk.net!ict.pwr.wroc.pl!news.task.gda.pl!not-for-mail
From: "Piotr Kolodziej" <pkol@otago.gda.pl>
Newsgroups: comp.databases.oracle.server
Subject: Re: import buffer > 256k?
Date: Mon, 26 Apr 1999 10:19:45 +0200
Organization: No organization.
Lines: 30
Message-ID: <7g17vp$pmc$1@korweta.task.gda.pl>
References: <37237FDE.78FD8D49@intercall.com>
Mime-Version: 1.0
Content-Type: text/plain;
 charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Trace: korweta.task.gda.pl 925115193 26316 195.116.21.33 (26 Apr 1999 08:26:33 GMT)
X-Complaints-To: abuse@task.gda.pl
NNTP-Posting-Date: 26 Apr 1999 08:26:33 GMT
X-Newsreader: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

David Spaisman wrote in message <37237FDE.78FD8D49@intercall.com>...
>1) sometimes import can be very slow if there are indices to
>build/rebuild. How can I speed import up?

Improve speed of index creation. First of all, make sort_area_size
as large as possible. It is very reasonable to allow tens of megabytes
of sort_area_size at the import time (if free RAM is available).
Next, ensure using sort_direct_writes and consider using temporary
tablespace.
If it is not enough, you may perform import without index creation
but with indexes file script created instead. Then you might re-edit
it to enforce NONRECOVERABLE index creation.

>2) Can I use 512k as a buffer size? Can I use anything larger? Has
>anyone encountered this concern?

Yes. I used up to 5M for example. Even you should use greater
in case of large rows (with long or long raw columns which size is
more than 0.5M).

>#) Has anyone loaded data with the import utility for a 2gb or 10 gb
>database?

Be sure. Many, many of us. Even with larger databases.

-- 
Piotr Kolodziej pkol@otago.gda.pl
Just my private opinion.