Abstract
Transactions are one of the features that set databases apart from file systems. In a file system, if you are in the middle of writing a file and the operating system crashes, that file will probably be corrupted, though there are “journaled” file systems and the like that may be able to recover your file to some point in time. However, if you need to keep two files synchronized, such a system won’t help—if you update one file and the system fails before you finish updating the second, your files won’t be synchronized.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Editor information
Rights and permissions
Copyright information
© 2010 Thomas Kyte
About this chapter
Cite this chapter
(2010). Transactions. In: Gennick, J., et al. Expert Oracle Database Architecture. Apress. https://doi.org/10.1007/978-1-4302-2947-6_8
Download citation
DOI: https://doi.org/10.1007/978-1-4302-2947-6_8
Publisher Name: Apress
Print ISBN: 978-1-4302-2946-9
Online ISBN: 978-1-4302-2947-6
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books