Re: Disable rollbacks

From: Roderick Manalac <rmanalac_at_oracle.com>
Date: 25 Aug 1994 00:03:52 GMT
Message-ID: <33gn59$33b_at_dcsun4.us.oracle.com>


peters_at_io.cpg.cdc.com (Robert A Peters) writes:
|> Barry Roomberg (barry.roomberg_at_compudata.com) wrote:
|> : Somebody claimed a while ago to have a method of disabling
|> : rollbacks during inserts (and I don't mean using discrete transactions).
|> :
|> : During an imp, I'd like to do this. I accept the fact that a failure
|> : will totally trash the database causing the need for re-initialization.
|> :
|> : Is this a dream, or is it possible?
|>
|> If you put a _disable_logging = true in the init.ora file, logging will
|> be turned off. This may also kill the writing to rollbacks.
|>
|>
|> Rob Peters

Very, very dangerous (unless you're willing like Barry to live with a trashed database and start over). Even if successful, it would be wise to take a cold backup and turn logging back on immediately.

That parameter only disables the writing of redo to the redo log files. Rollback is still generated as well as redo information in the redo buffer. So all that is gained is some IO to disk.

The safer method is to use the direct path option of SQL*Loader. I believe it even has an UNRECOVERABLE option (as of 7.0.16). It will bypass the SQL layer on insert, and not generate rollback and redo information (with the exception of keeping track of extent allocations). Eventually, most of this technology will be integrated into the import utility.

Roderick Manalac
Oracle Corporation Received on Thu Aug 25 1994 - 02:03:52 CEST

Original text of this message