In busy databases you may encounter this wait event. The general reason is the low redo log I/O performance or the slow interconnect connection.
As a solution of this wait event;
- You can increase the performance of Interconnect network. For example, instead of 1g cards, you can create an interconnect interface on 10g cards.
 - You can move Redo log files onto faster disks.
 - Or, you can set the value of the _cr_server_log_flush parameter to false. This is not suggested.
 
You can change the value of the parameter as follows.
1 2 3  | SQL> alter system set "_cr_server_log_flush"=false scope=both sid='*'; System altered.  | 
 ![]()
Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 