Re: Pinning a Table?

From: John P. Higgins <jh33378_at_deere.com>
Date: Sun, 27 Sep 1998 17:11:51 -0500
Message-ID: <360EB827.DA47F90C@deere.com>

The CACHE hint specifies that the blocks retrieved for the table in the hint are placed at the most recently used end of the LRU list in the buffer cache when a full table scan is performed. This option is useful for small lookup tables.

The NOCACHE hint specifies that the blocks retrieved for this table are placed at the least recently used end of the LRU list in the buffer cache when a full table scan is performed. This is the normal behavior of blocks in the buffer cache.

---------------------------------------------------------------------

If you use the CACHE hint but don't access the blocks often enough, they will age out anyway. Oracle8 offers a separate bufferpool you can assign to the 'keeper' tables.

Winnie Liu wrote:

How about caching the table in memory? By issuing alter table <tablename>
cache;, you can cache the table in memory. But  beware of your cache hit
ration performance. If it is deterioating.. it may not be such a good idea
after all!

Winnie

Chris wrote in message <360E6C96.9EBFD93A@reddogg.ne.mediaone.net>...
>I know that you can pin a PL/SQL object in the shared pool, but is there
>anyway to pin a table in memory?  If I have a table that I want to make
>sure is always in memory, how do I accomplish this task?
>
>Many thanks,
>Chris
>

  Received on Sun Sep 27 1998 - 17:11:51 CDT