If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Nope.
All the DML activity will be recorded in the redo logs either you run your database in ArchiveLog or in NoArchiveLog. You may only see problems in case of archive log mode when your redo logs are small in size and ARCH process cannot keep up with LGWR.

Like many prople you are confused about archiving and redo. Each is controlled by a different backgroud process do not affect each other. However if you disable archiving while the database in archive log mode, eventually all the redo log groups fill up and the database will hang.

Nologging on tables or tablespace does not disable import logging. James_cc is correct in saying that for slow imports, putting database in noarchivelog mode improves performance. Of course, the missing logs make the previous backups useless for complete recovery and a new full backup must be taken.

Originally posted by kris109 Nologging on tables or tablespace does not disable import logging. James_cc is correct in saying that for slow imports, putting database in noarchivelog mode improves performance. Of course, the missing logs make the previous backups useless for complete recovery and a new full backup must be taken.

Ah, you were talking about Import the utility -- I interpreted it as the generic process of loading external data, as through SQL*Loader or whatever. Okey dokey.