well I havent used sql loader direct load but as far as I know when you do direct load users cannot perform DML on those objects. The way to ensure this? Do it when the database activity is low if it is 24x7 database, otherwise do it at early mornings!
Originally posted by anuragmin I tried this but still it is generating logs.
There will always be *some* redo logs generated even during the nologged opereations. But the amount of redo generated should be *much* less then normal.
During nologged operations undo information is still written into RB segments and this undo entries are still fully logged. Also the data dictionary operations caused by unlogged operations (extent allocation etc) are still logged.
Also when reading the documentation I saw
"To use a direct path load (with the exception of parallel loads), SQL*Loader must have exclusive write access to the table and exclusive read/write access to any indexes"
It means that during direct path load the table is being locked in the exclusive mode, so other session can still perform reads on that table, but can't perform DMLs. Indexes belonging to the table that is being loaded are marked as UNUSABLE during the direct path load, so they can't be used by other session even for reads.
[Edited by jmodic on 06-11-2001 at 03:54 PM]
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?