When a user commits a transaction, the transaction is assigned a system change
number (SCN), which Oracle records along with the transaction’s redo entries in the
redo log. SCNs are recorded in the redo log so that recovery operations can be
synchronized in Real Application Clusters and distributed databases.
In times of high activity, LGWR can write to the redo log file using group commits. For
example, assume that a user commits a transaction. LGWR must write the
transaction’s redo entries to disk, and as this happens, other users issue COMMIT
statements. However, LGWR cannot write to the redo log file to commit these
transactions until it has completed its previous write operation. After the first
transaction’s entries are written to the redo log file, the entire list of redo entries of
waiting transactions (not yet committed) can be written to disk in one operation,
requiring less I/O than do transaction entries handled individually. Therefore, Oracle
minimizes disk I/O and maximizes performance of LGWR. If requests to commit
continue at a high rate, then every write (by LGWR) from the redo log buffer can
contain multiple commit records.
当用户提交一个事务时 , 将被记录一个SCN , 同样也记录在重做日志文件中 .
当系统处于高数位活动量时 , LGWR可以使用名为组提交的机制来减少磁盘I/O .
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/10599713/viewspace-979921/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/10599713/viewspace-979921/
本文详细介绍了在Oracle数据库中,事务提交时如何分配系统变更号(SCN),以及SCN如何与事务的重做条目一起记录在重做日志中。此外,还探讨了在高并发环境下,LGWR如何通过组提交的方式减少磁盘I/O操作,以此提高系统性能。
1910

被折叠的 条评论
为什么被折叠?



