cursor mutex s on insert statement
Hello,
Top User Events:
Event Event Class__________________% Event
CPU + Wait for CPU_________________47.66
cursor: mutex S Concurrency__________24.00
latch: shared pool Concurrency_________12.76
db file sequential read User I/O__________7.07
SQL*Net message from dblink Network___1.64
I've seen "cursor: mutex s" latch on active session history report (ashrpt.sql), it seems my db become 24% slower because of this latch. Am i right?
I googled around for hours and found the query and objects related to this latch.
INSERT INTO LGTXN( LogDate, TxnDate, SystemID, SourceCode, BrchNo, UserNo, HostName, HostIP, HostMAC, TxnCode, ParentTxnCode, TxnType, TxnDesc, Reserved1, Reserved2, SQL, Reserved3, ResultType, ResultDesc, SEQUENCE, Reserved4, Duration) values (:1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14, :15, :16, :17, :18, :19, :20, :21, :22)
Users are inserting to this log table on every transaction. By the time, there are 1300 total users and 15 active users. This table is monthly partitioned and 56Gigabytes of data is in the tablespace in which LB3TXN exists. Don't know how many rows are there.
Somebody plz help me to relief this "cursor mutex S" latch. Googled for hours and can't find exact solution to relief. Can making table partition daily basis (smaller partitions), or distributing table datafiles along separate disks help it?