本文探讨了在数据库中使用 FORCE LOGGING 模式的性能影响。此模式可能导致性能下降，但能确保完整的介质恢复。文章分析了介质故障的可能性、未记录直接写入无法恢复的严重性以及强制日志记录导致的性能下降是否可接受。
Performance Considerations of FORCE LOGGING Mode
FORCE LOGGING<wbr> mode results in some performance degradation. If the primary<br> reason for specifying<wbr> FORCE LOGGING<wbr> is to ensure complete media recovery, and<br> there is no standby database active, then consider the following:<br> ■ How many media failures are likely to happen?<br> ■ How serious is the damage if unlogged direct writes cannot be recovered?<br> ■ Is the performance degradation caused by forced logging tolerable?<br> If the database is running in<wbr> NOARCHIVELOG mode, then generally there is no benefit<br> to placing the database in<wbr> FORCE LOGGING<wbr> mode. Media recovery is not possible in<br> NOARCHIVELOG mode, so if you combine it with<wbr> FORCE LOGGING , the result may be<br> performance degradatio n with little benefit </wbr></wbr></wbr></wbr></wbr></wbr></wbr>
FORCE LOGGING<wbr> mode results in some performance degradation. If the primary<br> reason for specifying<wbr> FORCE LOGGING<wbr> is to ensure complete media recovery, and<br> there is no standby database active, then consider the following:<br> ■ How many media failures are likely to happen?<br> ■ How serious is the damage if unlogged direct writes cannot be recovered?<br> ■ Is the performance degradation caused by forced logging tolerable?<br> If the database is running in<wbr> NOARCHIVELOG mode, then generally there is no benefit<br> to placing the database in<wbr> FORCE LOGGING<wbr> mode. Media recovery is not possible in<br> NOARCHIVELOG mode, so if you combine it with<wbr> FORCE LOGGING , the result may be<br> performance degradatio n with little benefit </wbr></wbr></wbr></wbr></wbr></wbr></wbr>
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
