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.)

Question

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.)

Accepted Answer

B. Bind variables are not used for similar queries, causing hard parses. E. The CURSOR_SHARING parameter is set to EXACT, which does not allow similar queries to

Answer

A. The I/O performance is slow.

Answer

C. Repeated access to a small number of blocks.

Answer

D. Excessive time is spent on finding cached cursors in the library cache.

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…

Question

Options

How the community answered

Community Discussion