RelationalDBDesignRelationalDBDesign 





Shared Pool   «Prev  Next»
Lesson 10

Tuning the shared pool Conclusion

This module has focused on tuning the Oracle shared pool. We have looked closely at broader tuning issues and those specifically related to the library cache. Now you should be able to:
  1. List shared pool tuning techniques
  2. Pin packages in the shared pool
  3. Reserve space for large objects with shared_pool_reserved size
  4. Find high-use packages
  5. Gather information about the number of reloads required
  6. Detect library cache contention
  7. Determine library cache misses and parse calls for SQL
  8. Understand SQL re-use in the library cache


New terms

Here are some terms from this module that may have been new to you:
  1. pinning packages: The process of keeping packages inside the library cache
  2. estat-bstat utility: Oracle begin statistics (utlbstat.sql) and end statistics (utlestat.sql). These are used to create an elapsed-time snapshot of Oracle activity.
  3. shared SQL area: The shared SQL area is used to keep and process SQL statements and PL/SQL code.
  4. library cache miss ratio: Represents the ratio of the sum of library cache reloads to the sum of pins.
In the next module, we will look at tuning the Oracle buffer cache.

Shared Pool Concepts - Quiz

Before you go on, click the Quiz link below to complete one last quiz for this module.
Shared Pool Concepts - Quiz