Re: Cloning 21 GB Table - Review Approach please

  • From: Tim Gorman <tim@xxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 10 Mar 2005 15:57:40 -0700

> Will Arhive Redo Log be generated by the INSERT /*+ APPEND */ Command if =
> the Target Table has been PRE-Created with NOLOGGING?

No.  Won't generate any "undo" either.

> Any possibility of giving Hint for NOLOGGING in the INSERT Command ?


Why not use the built-in parallelism of Oracle?  Unless you've left
PARALLEL_MAX_SERVERS at the default of 5, you can add the PARALLEL hint to
both the INSERT and SELECT clauses.  You might also want to precede with
ALTER SESSION ENABLE PARALLEL DML and (of course) succeed with a COMMIT...

    alter session enable parallel dml;
    insert /*+ append nologging parallel(x, 4) */ into <target> x
    select /*+ full(y) parallel(y, 4) */ ... from <source> y;

No faster way to clone.  Your mileage may vary, but if you have a decent
sized box it shouldn't take more than 60-90 mins, tops...


Other related posts: