Re: PINS vs GETS

I've never completely figured out. The question is, how do we explain why most of the time SQL AREA and sometimes TABLE/PROCEDURE in v$librarycache have a lower value for gets than for pins? Another explanation of gets is attempts to locate the SQL (or TABLE/PROCEDURE definition) in library cache, which is consistent with your explanation. But wouldn't you expect higher gets? Maybe this get count is hard parse count? On my database it's smaller than "parse count (total)" and much greater than "parse count (hard)" in v$sysstat.

Yong Huang
yong321_at_yahoo.com

"Howard J. Rogers" <dba_at_hjrdba.com> wrote in message news:<3c658472$0$14524$afc38c87_at_news.optusnet.com.au>...
> Think of a GET as a parse, and a PIN as an execution.
>
> SQL statements have to be parsed first, then executed. A 'gethit' means
> that you didn't actually have to parse the SQL fresh, because an existing
> execution plan for an identical SQL statement was already in the library
> cache, and you were permitted to re-use it. It was still a "get", though,
Received on Sun Feb 10 2002 - 00:55:44 CST