Bad Timos Perfomance In PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS
(Doc ID 1160163.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
During an Authorization call, the following "step" in opstack timing is observed (full logs to be attached):
0.077917400 ....Enter PCM_OP_RATE_GET_PRODLIST (0x0)
0.078031650 .....Enter PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS (0x0)
0.078476500 ......Enter PCM_OP_READ_FLDS (0x400)
0.078489900 ......Exit PCM_OP_READ_FLDS (0x400) - from cache
0.078829850 ......Enter PCM_OP_SEARCH (0x40400)
0.247721000 ......Exit PCM_OP_SEARCH (0x40400) - from DM 0.0.0.1 --->
This is DM_TIMOS (no query observed on DM_Oracle)
0.254852150 .....Exit PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS (0x0)
0.258040100 ....Exit PCM_OP_RATE_GET_PRODLIST (0x0)
0.078031650 .....Enter PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS (0x0)
0.078476500 ......Enter PCM_OP_READ_FLDS (0x400)
0.078489900 ......Exit PCM_OP_READ_FLDS (0x400) - from cache
0.078829850 ......Enter PCM_OP_SEARCH (0x40400)
0.247721000 ......Exit PCM_OP_SEARCH (0x40400) - from DM 0.0.0.1 --->
This is DM_TIMOS (no query observed on DM_Oracle)
0.254852150 .....Exit PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS (0x0)
0.258040100 ....Exit PCM_OP_RATE_GET_PRODLIST (0x0)
No query is observed on DB (using DM_DEBUG3=0xFF).
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |