Sorry to hop on to your post, but I have a similar question for the
I would also like to know if there is a way to do a SQL*Load which does
not create ARCHIVE logs. We have one table which is truncated and fully
reloaded on a regular basis, but we do not need to recover it in case of
failure (becuase we can recreate it by other means). This table is
large, and therefore creates HUGE archives, which we don't need.
Currently we keep this table in a seperate instance with ARCHIVELOG
disabled, but running two instances wastes memory because of the
dedicated memory for the SGA.
>It has recently been brought to my attention that on some DBMS (Sybase,
>others) the operations like TRUNCATE or direct SQL*Loader load will
>invalidate the archives generated after this operation. The reason being
>that such operations are not logged, and therefore cannot be reproduced
>later in case of media failure recovery. I did not find any warning in
>Oracle manuals, and, luckily didn't have a chance to check it in real
>Does anyone have any comments on how Oracle handles the issue?
-- Keith Moore
KMA Computer Solutions, Inc.
* When the project must be saved at all costs: *
* KMA Computer Solutions, Inc. Project Troubleshooting/Recovery *