Deal of The Day! 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 supporting a mixed workload is hosted on a server with 64 CPUs.

A large number of free buffer waits and buffer busy waits occur affecting performance.

The buffer cache size was then increased but after a few hours, the same wait events occur more often than before the change.

Examine these parameter settings:

Which two actions can help reduce the number of these waits7

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:

Graham
2 days ago
Increasing the buffer cache size? What is this, the 90s? Let's move on to some 21st-century troubleshooting techniques, shall we?
upvoted 0 times
...
Lisha
8 days ago
I'm going to go with options C and D. Seems like the database needs more I/O throughput, and doubling the number of DBWR processes could help with that. Although, 64 DBWR processes might be overkill - maybe 32 would be a better compromise.
upvoted 0 times
...
Lindsey
11 days ago
I'm surprised they haven't mentioned anything about the CPU utilization. With 64 CPUs, I wonder if the database is even using all that processing power effectively. Maybe they need to look into their SQL statements or indexing as well.
upvoted 0 times
...
Carry
15 days ago
The question mentions a 'mixed workload,' so I'm not sure increasing MEMORY_TARGET is the best approach. Adjusting the I/O settings like the multiblock read count or the number of DBWR processes seems more promising.
upvoted 0 times
...
Franklyn
17 days ago
Increasing the buffer cache size doesn't seem to have helped, so that's probably not the solution. I think increasing the DB_FILE_MULTIBLOCK_READ_COUNT or the number of DBWR processes could help reduce the waits.
upvoted 0 times
...
Bernardine
17 days ago
I'm not sure about that, maybe increasing the size of MEMORYTARGET could also be a good solution.
upvoted 0 times
...
Verona
19 days ago
I agree with Goldie, that seems like a good option to reduce the waits.
upvoted 0 times
...
Goldie
27 days ago
I think increasing the value of DB_FILE_MULTIBLOCK_READ_COUNT to 128 could 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