Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-084 Topic 1 Question 6 Discussion

Actual exam question for Oracle's 1Z0-084 exam
Question #: 6
Topic #: 1
[All 1Z0-084 Questions]

A database instance is suffering poor I/O performance on two frequently accessed large tables.

No Big Table caching occurs in the database.

Examine these parameter settings:

Which are two actions either one of which will allow Big Table caching to occur?

Show Suggested Answer Hide Answer
Suggested Answer: C, D

Big Table caching is a feature that allows frequently accessed large tables to be cached in memory to improve I/O performance. From the parameter settings provided, Big Table caching is not occurring because DB_BIG_TABLE_CACHE_PERCENT_TARGET is set to 10, which is the minimum threshold for enabling the feature, but the size of the cache is too small for the big tables to be effectively cached.

To enable Big Table caching, one of the following actions could be taken:

C (Correct): Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25. This action would allocate a larger percentage of the buffer cache for storing big tables, which could allow for caching large tables and thus improve I/O performance.

D (Correct): Increasing DB_CACHE_SIZE to 1G. Since the size of the buffer cache is a determining factor for how much data can be cached, increasing this parameter would provide more memory space for big tables to be cached.

Options A, B, E, and F will not enable Big Table caching because:

A: Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to 50 without adjusting the overall size of the cache might still not be sufficient if the DB_CACHE_SIZE is not large enough to hold the big tables.

B: Setting DB_KEEP_CACHE_SIZE to at least 50M only specifies a separate buffer pool for objects with the KEEP cache attribute and does not affect Big Table caching.

E: and F: Changing the PARALLEL_DEGREE_POLICY to ADAPTIVE or AUTO influences the behavior of parallel execution but does not directly enable or influence Big Table caching.


Oracle Database Performance Tuning Guide: Big Table Caching

Oracle Database Reference: DB_BIG_TABLE_CACHE_PERCENT_TARGET

Oracle Database Reference: DB_CACHE_SIZE

Contribute your Thoughts:

Pete
6 months ago
I think increasing DB_CACHESIZE to 1G could also improve I/O performance.
upvoted 0 times
...
Rutha
6 months ago
But wouldn't increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25 also be a valid solution?
upvoted 0 times
...
Angelo
7 months ago
I disagree, I believe setting DB_KEEP_CACHE_SIZE to at least 50M is the better option.
upvoted 0 times
...
Rutha
7 months ago
I think increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 50 might help with Big Table caching.
upvoted 0 times
...
Sherita
7 months ago
I'm not sure about those options. What about increasing DB_CACHESIZE to 1G?
upvoted 0 times
...
Dana
7 months ago
I believe increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25 could also work.
upvoted 0 times
...
Gerald
7 months ago
I disagree, setting DB_KEEP_CACHE_SIZE to at least 50M could also be a solution.
upvoted 0 times
...
Celestina
7 months ago
I think increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 50 might help with Big Table caching.
upvoted 0 times
...
Quiana
8 months ago
Exactly! The question is specifically asking about Big Table caching, so I think the options that directly address that, like increasing the DB_BIG_TABLE_CACHE_PERCENT_TARGET, are the way to go. *nods in agreement*
upvoted 0 times
...
Chau
8 months ago
I'm not so sure about the PARALLEL_DEGREE_POLICY options. I mean, setting it to ADAPTIVE or AUTO might help with parallelism, but I don't think that's the core issue here. We need to focus on the caching, right?
upvoted 0 times
...
Daniel
8 months ago
Hmm, I don't think increasing the DB_CACHESIZE to 1GB is the best option here. That seems a bit overkill, especially if we're just dealing with two frequently accessed large tables. I'd stick with the DB_BIG_TABLE_CACHE_PERCENT_TARGET approach.
upvoted 0 times
...
Alberto
8 months ago
Aren't we forgetting about DB_CACHESIZE? Increasing that to 1GB could also help with the performance issues, no? I mean, the more cache, the better, right? *chuckles*
upvoted 0 times
Ezekiel
7 months ago
I think both could be beneficial. Maybe we should consider increasing both parameters.
upvoted 0 times
...
Cecilia
7 months ago
But what about DB_BIG_TABLE_CACHE_PERCENT_TARGET? Would increasing that also help?
upvoted 0 times
...
Tony
7 months ago
Definitely, increasing DB_CACHESIZE to 1GB could improve performance.
upvoted 0 times
...
...
Marsha
8 months ago
I agree, increasing the DB_BIG_TABLE_CACHE_PERCENT_TARGET seems like the most logical choice here. But I'm also curious about setting the DB_KEEP_CACHE_SIZE to at least 50M. That might be another viable option.
upvoted 0 times
...
Huey
8 months ago
Hmm, this question seems a bit tricky. I'm not entirely sure about the correct answer, but I think increasing the DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 50% might be a good option. That should help with the caching of the large tables, right?
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77