gc buffer busy acquire
A reader, January 18, 2022 - 5:25 pm UTC
Thanks for coming back.
I am clear on point 2 and thanks for sharing those parameters.
But for point one, can I ask some more questions:
1. When we checked the ASH report, top DB reports section, its pointing to Index related to inserts statements:
Event % Event Object Name (Type)
gc buffer busy release 6.25 SIEBEL.S_AUDIT_READ_P1
gc buffer busy release 2.79 SIEBEL.S_AUDIT_READ_M4
what does it mean?
2. Also top blocking session in ASH report shows "enq: TX - index contention".
So not sure what to check further.
Thanks
January 19, 2022 - 12:58 am UTC
A possibility is that you have an index with an ascending key (sequence, timestamp etc) and thus multiple inserts are competing for the "leading" leaf block.
You can attack this with a few options, generally the most scalable one being partitioning the index. You can see examples of that in the latter half of a video I did on physical design