Slide
‹#› of 37
Why is performance affected? (1)
uDatabase
running in ARCHIVELOG
ØAll
DML against SUPPORT table recorded
ØFilled
up about 85% of all logs!
uAll
support changes must be persistent.
ØExtra
COMMITS occurred
ØLOG FILE SYNC wait event count skyrocketed
uTable
had primary key (ID from a sequence)
ØDue
to DML activity from hundreds of sessions, every 15
minutes, the database logged a deadlock.
ØVery
high contention on some index blocks
