Copy a very big table from one database to other - Page 2
DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Copy a very big table from one database to other

  1. #11
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    ALTER TABLE tab1 NOLOGGING

    only works for direct load, i.e not for copy or import

    you either drop or keep index but you cannot set it to unusable, copy wont work

  2. #12
    Join Date
    Dec 2002
    Location
    Bangalore ( India )
    Posts
    2,434
    Originally posted by pando
    spool to flat file

    load with sql loader, direct path if possible, if not split the flat file into 5 or 6 files and load with sql loader
    This is the best method....rather than DB link or imp/exp.

    Abhay.
    funky...

    "I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."

    "Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"

  3. #13
    Join Date
    Apr 2002
    Location
    Germany.Laudenbach
    Posts
    448
    Hi,
    when export lasts 1 hour and import lasts days the n the index-build should be the problem.

    So increase your sort_area_size ( under 9i ) for example to 256M or more so that data can more sorted in memory then on temp-tablespace.
    with 9iR2 increase the PGA_AGGREGATE_TARGET to 256M or more

    Use this parameter to
    determine the optimal size of each work area allocated in AUTO mode (in other
    words, when WORKAREA_SIZE_POLICY is set to AUTO.

    * Try to seperate the index-build and create them with nologging

    Another problem of lacking writes could be
    * size of log_buffer
    * location, number and size of logfiles
    * Disk-layout

    Orca

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width