My Oracle Support Banner

AAA Opcode Latencies During Billing Delay Time (Doc ID 1253824.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: and later   [Release: 7.3.0 and later ]
Information in this document applies to any platform.


Standard TCF AAA opcode latencies show significant differences during the delayed billing period (i.e. before the delayed billing day is reached; in a single-DOM account base configuration), with respect to the rest of month processing (i.e. when all bills are finalized, past the delayed period). A difference in about 1-to-10 is seen in the overall opcode execution times.

Apparently, the “pre-delay” execution accumulate delays at each call accessing the DM-DB, as shown for example in the following comparison of opstack fragments, with the first OP_SEARCH in the opstack already showing a 1-to-10 difference in latency:


0,000000000 Enter PCM_OP_TCF_AAA_STOP_ACCOUNTING (0x0)
0,000091293 .Enter PCM_OP_ACT_FIND (0x0)
0,000433263 ..Enter PCM_OP_SEARCH (0x40000)                          
0,054648015 ..Exit  PCM_OP_SEARCH (0x80040000) - from DM  


0,000000000 Enter PCM_OP_TCF_AAA_STOP_ACCOUNTING (0x0)
0,000100255 .Enter PCM_OP_ACT_FIND (0x0)
0,000372455 ..Enter PCM_OP_SEARCH (0x40000)
0,004868147 ..Exit  PCM_OP_SEARCH (0x40000) - from DM        


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.