Specifically on full DB caching
Tesla AR, November 16, 2016 - 3:14 pm UTC
Can you shed some light on Full Database Caching which is available from 12c onwards.?
1. When should one prefer over the normal usage?
2. Is it like in-memory where it stores all the data in the RAM?
3. When using full-database caching, should I specifically mention the buffer cache size for it to hold the full data?
Thanks in advance!!
November 17, 2016 - 2:47 am UTC
1. When should one prefer over the normal usage?
If your I/O subsystem is a significant bottleneck. Even with a large buffer cache, we might do lots of things direct from disk. Full database caching endeavours to avoid any such activity.
2. Is it like in-memory where it stores all the data in the RAM?
No. In-memory is a reformatting/restructuring of existing row data into a new format.
3. When using full-database caching, should I specifically mention the buffer cache size for it to hold the full data?
As a minimum, I would set db_cache_size so I know that there is a minimum size the cache will be kept to.
Reporting and full db caching
Tesla AR, November 19, 2016 - 3:15 am UTC
Say I have an reporting database where only reporting runs, fetching of reports etc. Only selects, in that case, if I enable full database caching and I set a high value to db_cache_size w.r.t the RAM, the response of the queries would be high compared to database without full database caching?
November 19, 2016 - 3:44 am UTC
It depends on the server and the usage of it. I have seen queries full based in RAM run *slower* than queries that come off disk, because of increased competition for buffers.
The answer is simple: Benchmark it.