Hi Tanel,
We faced the issue of library cache latch contentions due to which CPU was 0% idle continuously. There was one index rebuild session which was holding the library cache lock. Others were waiting with “library cache: Mutex X”. Some times I was able to see other session coming and going with “Library cache lock”. But index rebuild was there.
I was not able to check which session was holding lock. Whenever I used to run the query to check the holder of library cache lock, it was displaying “library cache: Mutex X” and never used come back.
So I decided to kill the index rebuild. But it’s Journal table did not clean up after killing the index rebuild and still I was able to see that index rebuild session which was holding the Library cache lock. Manual clean up of the journal table was also stuck.
Here my question is what can we do in this case? This database was critical. I tried for around 25 mins and then decided to go for failover of the database to standby.
Thanks,
Ashish