Set [no]logging Option
To suspend transaction logging for the current session, issue the set nologging statement; to resume logging, issue the set logging statement. To issue this statement, you must be the DBA of the database to which your session is connected.
Suspending transaction logging can improve the performance of large batch updates. However, use set nologging with extreme caution, and consider checkpointing the database before suspending logging. Be advised that, when transaction logging is suspended:
• The abort statement has no effect.
• Any error (including errors resulting from a database statement, forced abort, deadlock, or timeout) leaves the database in an unknown state.