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

Thursday Feb 15th 2007 by Staff

A new option to the COMMIT statement in Oracle 10g can defer the writing of committed data to the online redo log files. This involves a risk of data loss, but...


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

Mobile Site | Full Site
Copyright 2017 © QuinStreet Inc. All Rights Reserved