One oddity explained

A few weeks ago I wrote about four oddities I encountered when doing a little research into several 11g features in this blog post. And this morning I read a very thorough article about the result cache here on oracle-developer.net, which addresses the first oddity by this sentence:

The cache is allocated directly from the shared pool but is maintained separately.

Although Adrian does not state how he came to know this, it sounds as a simple but plausible explanation of why the Concepts Manual shows the result cache as an area separate from the shared pool and why the dbms_result_cache.memory_report tells us it is memory from the shared pool.

At the end of the article, three links to Pythian blog posts are shown. In short, they are a warning that the result cache may not be as scalable as one might hope. Because I enjoyed reading those posts as well, here are the links: post 1, post 2 and post 3.