Oracle Database 10g Release 2 introduced the commit write facility, which gives the appearance a commit has completed when it really hasn't. If commit times are taking too long (log file sync will be the top wait event) and the application can survive the possibility of lost data5 in an unfortunate instance failure, then technically, one of the commit write options may provide the extra performance boost you need. But please, ensure your application and the business can tolerate the potential loss of committed data. As I tell people, slower performance is better than no performance.

The trusted standard commit command is the same as commit write immediate, wait, but there are three other alternatives. Each can be put into effect in any of the following ways:

The following snippet shows the various ways to interactively use and set the commit_write options to an immediate and nowait setting.