The world’s Largest Sharp Brain Virtual Experts Marketplace Just a click Away
Levels Tought:
Elementary,Middle School,High School,College,University,PHD
| Teaching Since: | Jul 2017 |
| Last Sign in: | 337 Weeks Ago |
| Questions Answered: | 15833 |
| Tutorials Posted: | 15827 |
MBA,PHD, Juris Doctor
Strayer,Devery,Harvard University
Mar-1995 - Mar-2002
Manager Planning
WalMart
Mar-2001 - Feb-2009
Oracle refers to a transaction log as a redo log. When a transaction is in progress, changes in data items are recorded in memory in a redo log buffer. When any transaction commits, the redo log buffer (which contains changes that all transactions have made) is written to a redo log file. Curiously, the commit does not force anything to be written to the actual database files. Occasionally, a background process called Database-Writer will write modified buffers out to database files.
Suppose the system crashes. How could the redo log file be used to undo a transaction that was only partially completed and had not committed?
Suppose the system crashes. How could the redo log file be used to ensure committed transactions are actually written to the database files?
Question 2 options:
----------- ----------- H-----------ell-----------o S-----------ir/-----------Mad-----------am ----------- Th-----------ank----------- yo-----------u f-----------or -----------you-----------r i-----------nte-----------res-----------t a-----------nd -----------buy-----------ing----------- my----------- po-----------ste-----------d s-----------olu-----------tio-----------n. -----------Ple-----------ase----------- pi-----------ng -----------me -----------on -----------cha-----------t I----------- am----------- on-----------lin-----------e o-----------r i-----------nbo-----------x m-----------e a----------- me-----------ssa-----------ge -----------I w-----------ill----------- be----------- qu-----------ick-----------ly