These are notes I have found, taken, and used many times...and not always all of them at the same time...what these parameters "undo" you might have to "redo: later; index, stats, etc. Same of these are not very good for regularly reoccurring IMPorts...I tend to start hacking when I need to move a lot of data, one time, fast(er). hth Chris Marquez Oracle DBA ----------------------- Faster IMPORTS ----------------------- Set IMP parameter COMMIT = Y. Set IMP parameter RECORDLENGTH >= EXP RECORDLENGTH value. Set IMP parameter BUFFER = MB (Set in the MB range not KB range) Set IMP parameter STATISTICS = NONE (9i, n/a 8i) Set IMP parameter RECALCULATE_STATISTICS = N. (8i, n/a 9i) Set IMP parameter ANALYZE = N. (8i, n/a 9i) Set IMP parameter INDEXES = N (Import them later...separately) Set init.ora parameter LOG_ARCHIVE_START = FALSE *&* alter database noarchivelog; Set init.ora parameter _disable_logging = TRUE (Warning, this could be dangerous and unrecoverable in failure. Backup immediately after import) Use Locally Managed Tablespaces on target database. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of A Joshi Sent: Mon 6/6/2005 10:08 AM To: oracle-l@xxxxxxxxxxxxx Subject: ** import tuning Hi, I have a export taken with direct=y. This is done setting a high recordlengh = 64K. When importing using this export sould I set recordlength or buffer? How high is Ok for buffer? I am on 817 on sun 5.8. I need to do this operation frequently and need to tune it. Basically is export taken with direct option any different from regular export? Or is it better to just use regular export (non direct) with high buffer and use the same buffer for import. thanks for your help. --------------------------------- Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l