Stop_accounting Returns Timeout, But No Events Committed to DB

(Doc ID 851961.1)

Last updated on JUNE 05, 2018

Applies to:

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

Goal

The following scenario is observed in a real-time AAA-Gateway production setup:

- a call termination request is issued from SCP to AAA-Gateway
- the AAA-Gateway returns with a timeout to SCP (i.e. the stop-accounting opcode call hasn't returned within the configured timeout)
- the opcode has not left a trace on DB as if the DB commit was missing
- no error is found in either CM or DM pinlogĀ 

A relatively higher number of "missing" events is closely related to the "high batch" times, i.e. those timeframes during which a performance decrease in the CM-DM-DB chain brings to timeout responses from the AAA-Gateway, but with the corresponding event found on DB.

How can we explain these "missing commit" events and how can we minimize them?

Solution

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