RE: Table cache info please.

alter table XX cache does not cause that table to be cached in memory. It means that IF a full table scan is done on it, add the blocks read to the MRU end of the buffer cache chain rather than the LRU end of the buffer cache chain. (which is the default functionality).
The blocks will be aged out of the buffer cache through the normal aging mechanism.

If you want to hold all of a table in memory, try using the BUFFER_POOL KEEP option.

> -----Original Message-----
> From: Ron Rogers [mailto:RROGERS_at_galottery.org]
> Sent: Wednesday, August 09, 2000 9:28 AM
> To: Multiple recipients of list ORACLE-L
> Subject: Table cache info please.
>
>
> Good morning team,
> I am thinking about caching a table that is used quite
> frequently by our applications and have a question that is
> puzzeling me.
> The table is truncated daily and reloaded with fresh
> information for the applications to use.
> Question: If I alter table xx cache the table, what effect
> does the truncate and reload have on the table cached in
> memory? Is it automatically recached after the truncate and
> reload or is the cached table in memory not truncated and
> reloaded until the first block is read and the difference in
> tables is detected?
> Thanks,
> Ron ROgers
> DBA OCP
> Atl.GA
>
>
> --
> Author: Ron Rogers
> INET: RROGERS_at_galottery.org
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
Received on Wed Aug 09 2000 - 09:56:21 CDT