|
|
by Craig Shallahamer Get the book here |
|
|
Craig Shallahamer's Blog
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. Please—Out 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. ------------------------------- Once subpools where introduced, and especially combined with the other solutions I've outlined, shared pool latch contention can be successfully resolved. If you want to rile an Oracle DBA, sneak up behind them and whisper, "4031." A 4031 error is Oracle saying to you, "I give up." Perhaps there is an, "I tried and I'm sorry" just before that, but it doesn't offer much consolation and surely doesn't stop the phone calls from angry users. Oracle has a tricky balancing act deciding when to give up and when to continue consuming CPU and holding latches. Over the years, the likelihood of Oracle running out of shared pool memory has decreased, but the chance of a 4031 error is still highly dependent on the amount of Oracle shared pool memory and the application. The following is an actual 4031 error message: Please—Out 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. |
Know what's important before it's too late!
OraPub's
Performance Training
is like no other...
More Class Pics...
Get student testimonials!