Abstract
As a developer, it’s often important to be able to measure how much redo your operations generate. The more redo you generate, the longer your operations may take, and the slower the entire system might be. You are not just affecting your session, but every session. Redo management is a point of serialization within the database. There is just one LGWR in any Oracle instance, and eventually all transactions end up at LGWR, asking it to manage their redo and COMMIT their transaction. The more it has to do, the slower the system will be. By seeing how much redo an operation tends to generate, and testing more than one approach to a problem, you can find the best way to do things.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsAuthor information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Thomas Kyte
About this chapter
Cite this chapter
Kyte, T., Kuhn, D. (2014). Investigating Redo. In: Oracle Database Transactions and Locking Revealed. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-0760-4_7
Download citation
DOI: https://doi.org/10.1007/978-1-4842-0760-4_7
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-0761-1
Online ISBN: 978-1-4842-0760-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books