direct load and direct load unrecoverable
From: <genegurevich_at_discover.com>
Date: Wed, 2 Jul 2008 11:41:22 -0500
Message-ID: <OF67DD391D.3745F118-ON8625747A.005AFC67-8625747A.005BAF22@discover.com>
Date: Wed, 2 Jul 2008 11:41:22 -0500
Message-ID: <OF67DD391D.3745F118-ON8625747A.005AFC67-8625747A.005BAF22@discover.com>
Helli everyone:
I have been reading information on Don Burleson's site about direct load
unrecoverable as a way to speed up
the load (http://www.remote-dba.net/teas_rem_util18.htm) among other
things. I have never used this parameter
(unrecoverable) in SQL*Loader before and I always though that SQL*Loader in
direct mode does not create any
archived logfiles and therefore if a database needs to be restored, the
tables that were loaded via SQL*Loader
in direct mode won't be restored. After reading this
· Use unrecoverable. The unrecoverable option (unrecoverable load data) disables the writing of the data to the redo logs. This option is available for direct path loads only It seems that a table that was loaded via SQL*Loader with direct mode (but not unrecoverable) will be "restorable" from a backup. Is that correct interpretation?
thank you
Gene Gurevich
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Jul 02 2008 - 11:41:22 CDT