Oracle Database 12c: Performance Management and Tuning — Question 1

You are administering a database that supports an OLTP workload. The CURSOR_SHARING parameter is set to EXACT for the instance. The performance of queries issued by one of the modules has degraded. The queries executed by the module are almost identical in syntax. To investigate, you analyze the latest
AWR report and find a large number of latch:shared pool wait events and also a high percentage of the hard parse elapsed time.
Which two can be reasons for this? (Choose two.)

Answer options

• A. The I/O performance is slow.
• B. Bind variables are not used for similar queries, causing hard parses.
• C. Repeated access to a small number of blocks.
• D. Excessive time is spent on finding cached cursors in the library cache.
• E. The CURSOR_SHARING parameter is set to EXACT, which does not allow similar queries to share a cursor.

Correct answer: B, C

Explanation

The correct answers are B and C. Option B is correct because not using bind variables for similar queries results in hard parses, which increases resource consumption. Option C is also correct, as excessive access to a small number of blocks can lead to contention and degrade performance. The other options are incorrect as they do not directly relate to the issues indicated by the AWR report in the context of the CURSOR_SHARING setting.