| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Import Question
Mike, your subject line is misleading since I think most readers will take
"import" to mean the imp utility.
R3load is beyond my experience but on the Oracle db side I would verify that the online redo logs were not switching excessively during the load.
With a conventional imp if the target table exists, is large, and has indexes defined on it then dropping the indexes, loading the table, and rebuilding the indexes as a separate step is often significantly faster than loading with the indexes in place. This may also be true for the R3load if you have the same conditions.
Good luck
-- Mark D Powell --
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Vergara, Michael
(TEM)
Sent: Friday, July 09, 2004 11:28 AM
To: oracle-l_at_freelists.org
Subject: RE: Import Question
Mark:
Oh...if only this were a conventional import!
This is an SAP system, and the export/import process uses a SAP-written utility called "R3load". That I know of, there are no settable parameters like the buffer parameter in an Oracle import.
R3load writes to a flat file than is encoded and compressed using SAP's proprietary programming. It works very well at the compression angle. A 1.5TB database exported out to just under 300GB of flat files.
The only tuning opportunities I have are on the database server. I can send out the whole initSID.ora file, but I thought that would be overkill for the first question.
Thanks for the support!
Mike
-
 |
 |