Which two actions can improve this?

Examine the output of the following query:
SQL> SELECT c.name,a.addr,a.gets,a.misses,a.sleeps,
2 a.immediate_gets,a.immediate_misses,b.pid
3 FROM v$latch a, v$latchholder b, v$latchname c
4 WHERE a.addr = b.laddr(+) and a.latch# = c.latch#
5 AND c.name LIKE ‘&latch_name%’ ORDER BY a.latch#;
LATCH NAME ADDR GETS MISSES SLEEPS IMMEDIATE_GETS IMMEDIATE_MISSES
———— ——– ——– ——- —— ————– —————-
shared pool 20016544 8520540 14112 3137 0 0
You calculated the Gets-to-Misses ratio, which is .99834, and this ratio is dropping over a period of
time.

Which two actions can improve this? (Choose two.)

Examine the output of the following query:
SQL> SELECT c.name,a.addr,a.gets,a.misses,a.sleeps,
2 a.immediate_gets,a.immediate_misses,b.pid
3 FROM v$latch a, v$latchholder b, v$latchname c
4 WHERE a.addr = b.laddr(+) and a.latch# = c.latch#
5 AND c.name LIKE ‘&latch_name%’ ORDER BY a.latch#;
LATCH NAME ADDR GETS MISSES SLEEPS IMMEDIATE_GETS IMMEDIATE_MISSES
———— ——– ——– ——- —— ————– —————-
shared pool 20016544 8520540 14112 3137 0 0
You calculated the Gets-to-Misses ratio, which is .99834, and this ratio is dropping over a period of
time.

Which two actions can improve this? (Choose two.)

A.
reducing hard parses

B.
increasing the size of the shared pool

C.
using only dedicated server connections

D.
setting the CURSOR_SHARING parameter to EXACT

E.
encouraging the use of more literal SQL statements



Leave a Reply 2

Your email address will not be published. Required fields are marked *


L. Zhu

L. Zhu

A is right. reducing hard parsing can improve hit ratio
B is right. increasing share pool size
C is wrong. MTS does not help
D is wrong. cursor_share to exact will even worse.
E is wrong. worse

So A.B are correct

ash

ash

gets to miss ratio value is calculated from gets-misses/gets