Chapter 9. Result Cache
In the last chapter, we learned quite a few techniques to tune PL/SQL code. By now, you must have got the idea that tuning is nothing less than an art that comes by practice and grows with experience. The better you understand the data and the application, the higher the probability of tuning the right areas. Most DBAs around the world are familiar with the commonly used tuning practices such as query rewriting, column indexing, instance optimization, materialized views, and PL/SQL code optimization.
As Oracle Database professionals, we might already be aware of multiple caches resident in the database instance architecture (to name a few: the buffer cache, library cache, dictionary cache, or recycle cache). Primarily, caches are meant to hold data so that the data access operations are served faster.
Oracle Database 11g Release 2 introduced a new cache component within the shared pool, known as the Server Result Cache, for a specific job. The Result Cache enables...
