Thank you . It seems to match our symptoms. (Big Rollback causing enq-ss
contention)
We were thinking about killing the system processes which are trying to
perform the rollback as we don't need that job anymore. Is that safe?
Or we have to either wait to let that finish and the new transactions may
move on by increasing the pga_aggregate_target as suggested in the note.
else drop and create temp tablespace.
On Thu, May 6, 2021 at 10:13 AM Chris Taylor <
christopherdtaylor1994@xxxxxxxxx> wrote:
I had to look up ENQ-SS on Oracle support. That's a sort segment
contention, usually encountered when SMON is really busy cleaning up a dead
/ killed transaction.
Oracle support has a few notes on this but the most applicable seem to
stop at 11.1 .
There is one note that says to try to increase PGA_AGGREGATE_TARGET
SS Sort Segment Enqueue: 'enq: SS - contention' (Doc ID 2601825.1)
Chris
On Wed, May 5, 2021 at 11:56 PM Lok P <loknath.73@xxxxxxxxx> wrote:
Hi All, Need some help, we had killed one of the long running sessions
which was running since ~8hrs+ , but after we kill that we see a lot of
"wait for a undo record" wait events but we ignored that thinking that will
run for sometime as because it will do rollback. But suddenly now we are
seeing "enq-SS contention" wait event in addition to "wait for a undo
record" and that is blocking all other application queries. So wondering
how we should mitigate this issue?
The version is 11.2.0.4 of Exadata.
Regards
Lok
