|
Dan: I believe the SQL on the outbound is eliminated. With DIRECT=Y, the Kernel performs I/O direct
to the DMP file versus generating the SELECT statements to retrieve the data and
then write out the data. That’s why
exports take far less time with DIRECT=Y. You are correct that Redo WILL be generated on the import side.
Thank
You Stephen
P. Karniotis Product Architect Compuware Corporation Direct: (248)
865-4350 Mobile: (248)
408-2918 Email: [EMAIL PROTECTED] Web: www.compuware.com -----Original
Message----- > Very interesting, except that I believe
you are wrong. ALL of my exports are done with direct=y option. I can
demonstrate very easily that there will be 'redo' generated when doing the
import by putting the importing database into archivelog mode and turning off
the archiver process. If redo is not being produced (as you state), why do I
see messages in the alert log telling me that the database is halted because
all my redo logs are full and need archiving? Have a nice day, The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. |
Title: RE: import question
- IMPORT QUESTION Seema Singh
- RE: IMPORT ... אדר יחיאל
- import ques... Malik, Fawzia
- RE: import ... Vikas Khanna
- RE: import ... Deshpande, Kirti
- RE: import ... Straub, Dan
- RE: import ... Hately Mike
- RE: import ... Karniotis, Stephen
- RE: import ... Joe Raube
- RE: import ... Khedr, Waleed
- IMPORT QUES... Hamid Alavi
- RE: IMPORT ... DENNIS WILLIAMS
- Re: IMPORT ... Stephane Faroult
