Re: Cache Hit Ratio

In article <34B29038.421759C9_at_quebim.com>, Lando wrote:

If you do attempt to pre-load data in the the db_block_buffers ensure that you are accessing via indexes and not using full table scans as you would then be wasting your time. (Table scans go into a 'reserved' part of the SGA just for table scans)

Always pin your packages and stored procedures. (DBMS_SHARED_POOL.KEEP)

Look at the CACHE option for table less that 5 oracle blocks.

regs

Neil Chandler

>One option you could experiment with would be to write and execute a
>script on startup that will cycle through and touch all of the relevent
>tables you are concerned with. Another option would be to use hot
>backups. Also, for small lookup type tables you may want to check out
>the cache option (this could also be done in a startup script along with
>pinning of packages, procedures, etc).
>
>M.Landa
>
>Someone wrote:
>
>> In my current setup I always bring down oracle for a cold backup every
>>
>> night. Of course, when Oracle starts up the cache hit ratio is low as
>>
>> the tables get read back into memory. I seem to recall a long time
>> ago
>> that someone in this newsgroup asked whether you could load tables
>> back
>> into memory or even perhaps take a snapshot of the SGA and reload it
>> when it restarts. Seems unlikely but hey, anyone have any ideas?
>
>
>
Received on Wed Jan 07 1998 - 00:00:00 CST