http://www.dba.5341.com/
http://www.dba.5341.com/
Hi,
If you think exporting
CLOBs are slow, wait till you import! It’s much much slower.
During imports, depending
on the size of your clob column, you may be able to get away with COMMIT=N. I’ve
found this to be much faster than COMMIT=Y. However, it means that you must
have a LARGE undo retention and tablespace, otherwise your import will fail.
The other trick we’ve
found is that even though we have clob columns defined in the tables, they are
actually empty. So doing a “sql unload” and sqlload without the
clob columns will cut down your times.
HTH,
Leng.
-------------------------
Date: Thu, 22 Jun 2006
19:35:23 -0700 (PDT)
From: A Joshi
<ajoshi977@yahoo.com>
Subject: ** table with clob
slow
Hi,
We have a big table and it has one
field with CLOB datatype. Doing an export on this table is very slow. I have
tried with different buffer sizes of 2MB - 250MB. It is still slow. Any way to
speed up export and other operations on the table like update,delete. Thanks
for your help.
------------------------------------------------------------------
Leng Kaing
Senior Oracle
DBA
Hansen
Technologies;
Ph:
+61-3-9840-3832
| Notice: This e-mail and any attachments are confidential and may contain legally privileged information and/or copyright material of Hansen Technologies Limited or third parties. Copying, distributing, disclosing, commercialising or otherwise acting in reliance on this e-mail and any attachments is strictly prohibited unless you are the addressee of this e-mail and have written permission to do so. If you have received this e-mail in error please delete this e-mail (including any copies and attachments) and contact Hansen Technologies Limited by return e-mail or by telephone on + 61 3 9840 3000. Any views expressed in this e-mail are those of the individual sender and may not necessarily reflect the views of or be a commitment by the organisation, except where the individual sender has the authority and expressly states them to be so. |