You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
The text below is an except from the book,
Oracle Performance Firefighting, written by
Craig Shallahamer of
OraPub, Inc.
Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click
here.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
-------------------------------
Figure 8-9. Shown are three ways to gather the SQL associated with the wait event log file sync, or with a slight modification, any wait event.
There are times when the application truly demands an immediate commit, which can result in a tremendous commit rate. For example, I know of systems where financial transactions arrive from multiple sources. The transactions are small, but because they are independent transactions, the legal and business rules require that each individual incoming transaction must be immediately committed to the database. In this situation, you have little choice but to devise a solution that does not involve changing the application.
Regardless of what you find, when experiencing significant log file sync waits, assume there is a rapid commit issue and find out why it is occurring. Understanding this will help you devise a better application and nonapplication solution strategy.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
|