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 10 Question 18 Discussion

Actual exam question for Oracle's 1Z0-084 exam
Question #: 18
Topic #: 10
[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:

Helaine
2 months ago
I'm with Ashton on this one. 25% cache target for Big Tables should do the trick. No need to go overboard with 50%.
upvoted 0 times
Celeste
1 months ago
Let's go with option C, increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25.
upvoted 0 times
...
Allene
2 months ago
I think increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25 is the way to go.
upvoted 0 times
...
Karan
2 months ago
I agree with you, 25% cache target should be enough for Big Tables.
upvoted 0 times
...
...
Lai
2 months ago
Ha! Parallel degree policy options E and F are just red herrings. We need to focus on the cache settings, not parallelism.
upvoted 0 times
Brandon
1 months ago
C) Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25
upvoted 0 times
...
Stefanie
2 months ago
Ha! Parallel degree policy options E and F are just red herrings. We need to focus on the cache settings, not parallelism.
upvoted 0 times
...
Tiara
2 months ago
B) Setting DB_KEEP_CACHE_SIZE to at least 50M
upvoted 0 times
...
Ernie
2 months ago
A) Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 50
upvoted 0 times
...
...
Dyan
3 months ago
Hmm, setting DB_KEEP_CACHE_SIZE to 50M seems a bit low. I'd try option D and bump up DB_CACHESIZE to 1G instead.
upvoted 0 times
Alyce
2 months ago
Let's go with option D and increase DB_CACHESIZE to 1G for better caching.
upvoted 0 times
...
Rhea
2 months ago
I think setting DB_KEEP_CACHE_SIZE to 50M might not be enough to address the issue.
upvoted 0 times
...
Ettie
2 months ago
I agree, increasing DB_CACHESIZE to 1G could help improve performance.
upvoted 0 times
...
...
Ashton
3 months ago
Looks like we need to increase the cache percentage for Big Tables. I'd go with option C - 25% seems more reasonable than 50%.
upvoted 0 times
Leonida
1 months ago
Let's go with option C then, it seems like a balanced choice.
upvoted 0 times
...
Krystina
2 months ago
I think option A might be too high, 25% with option C sounds like a safer bet.
upvoted 0 times
...
Nikita
2 months ago
But what about option A? Wouldn't increasing it to at least 50% be better?
upvoted 0 times
...
Whitley
2 months ago
I agree, option C seems like a good choice.
upvoted 0 times
...
...
Stanford
3 months ago
I think both options could work, but increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25 might be a good compromise.
upvoted 0 times
...
Helene
3 months ago
I disagree, I believe setting DB_KEEP_CACHE_SIZE to at least 50M is the way to go.
upvoted 0 times
...
Gerald
3 months ago
I think increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 50 will help.
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