Pin_log_flist Called By Many Opcodes In Many Libs Caused Major Perf Degradation
Last updated on JANUARY 14, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, CM
Even though CM loglevel is set to 1 [ log error messages only] , pstack output shows that pin_log_flist is getting called by many opcodes from many libraries, such calls to pin_log_flist function are causing major performance degradation.
Here the sample stack trace
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms