Trade risk for speed with Oracle 10g's asynchronous COMMIT

February 15, 2007

[From Builder.com]

One thing that Oracle DBAs know for a fact is that a transaction isn't committed until it is written to the online redo log files. If a COMMIT statement in an application completes, the application can trust that the data is protected against instance failure, and can be recovered by "rolling forward" the log files. In Oracle 10g, that's no longer always true.

The article continues at http://builder.com.com/5100-6388_14-6158695.html?tag=sc