Billing - Concurrency Issues (library Cache Lock)
(Doc ID 2910812.1)
Last updated on SEPTEMBER 28, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
For a couple of months now, during a billing period, it is observed that concurrency issues like library cache lock.
Analysis of Automatic Workload Repository (AWR) reports shows that the library cache lock wait events are caused by excessive parsing. The Structured Query Language (SQL) section shows that the b6u19bakp3znm sql_id is the top one.
How to avoid this ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document