For which two requirements can you always use the V$ACTIVE_SESSION_HISTORY
view?(Choose two.)
A.
to investigate intermittent performance problems in a session, only when the problem
lasted less than five minutes in the last twelve hours
B.
to find the exact number of executions of a specific query in a session in the last two
minutes
C.
to identify which module in an application was being executed in a session
D.
to identify a scheduler job that is not responding
E.
to find the amount of Program GlobalArchitecture (PGA) memory being currently
consumed by a session
agree
But answer E… PGA is Program Global Area not Architecture.
Maybe B and C
B,E
for B:
select session_id, session_serial#, count(sql_exec_id)
from v$active_session_history
where sql_id = ‘dr97hbjraumrm’
AND sample_time >= sysdate – interval ‘2’ minute
group by session_id, session_serial#;
sorry:) I mean B,C
BC
C,E
B is wrong. ASH buffer is populated by active sessions data which sampled with 1 second interval. If a short query (for example, with 50 ms average elapsed time) was executed many times between two samples, we can not find the exact number of its executions in a session.
If “Program Global Architecture (PGA)” is just a typo, then E – is correct.