RE: Disable redo writing
- From: "Amaral, Rui" <Rui.Amaral@xxxxxxxxxxxxxxxx>
- To: "'rjoralist2@xxxxxxxxxxxxxxxxxxxxx'" <rjoralist2@xxxxxxxxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 27 Jan 2011 13:39:52 -0500
There's also another point to consider which is statistics on indexes also
generate a lot of data not to mention slow performance - at least in 10.2 (just
got hit with that over the last 2 days and had to set
_optimizer_compute_index_stats=FALSE) might still be there for 11r1 too so best
check that out
Referring to
EXCLUDE=STATISTICS Or EXCLUDE=INDEX_STATISTICS During Datapump Import Still
Analyzes The Indexes [ID 793585.1]
Doesn't make mention of newer releases (and I didn't see anything regarding 11
when I looked) but I could have missed something.
Rui Amaral
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Rich Jesse
Sent: Thursday, January 27, 2011 1:34 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Disable redo writing
> You can set the tablespaces before import to NOLOGGING mode and enable
> logging after the import is done.
> I'm not sure about importing over network link, but if you run both
> expdp and impdp locally using PARALLEL parameter, then indexes are
> also created in parallel.
That still may not work, at least in 10gR1. From the docs
(http://download.oracle.com/docs/cd/B14117_01/server.101/b10825/dp_perf.htm#sthref423):
--
In the following circumstances, Data Pump cannot use direct path loading:
* A global index on multipartition tables exists during a single-partition
load. This includes object tables that are partitioned.
* A domain index exists for a LOB column.
* A table is in a cluster.
* A table has an active trigger.
* A table has fine-grained access control enabled in insert mode.
* A table contains BFILE columns or columns of opaque types.
* A referential integrity constraint is present.
* A table contains VARRAY columns with an embedded opaque type.
If any of these conditions exist for a table, Data Pump uses external tables
rather than direct path to move the data for that table.
--
The RI restriction would seem to be the most common gotcha. I never could get
Data Pump to use direct path inserts using the API over a database link, even
without any RI present. I ended up using it just for tables with LOBs and then
an INSERT/SELECT over the link with the APPEND hint for all other tables.
Quite the PITA!
Then again, this is on 10gR1 -- perhaps newer versions (still under primary
support!) work differently.
Rich
--
//www.freelists.org/webpage/oracle-l
NOTICE: Confidential message which may be privileged. Unauthorized
use/disclosure prohibited. If received in error, please go to www.td.com/legal
for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié.
Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière
d'aller au www.td.com/francais/avis_juridique pour des instructions.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
