AAA-Gw: Stop_accounting Returns Timeout, But No Events Was Committed To Db
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 10-May-2013***
The following scenario is observed in a real-time AAA-Gateway production setup:
- a call termination request is issued from SCP to AAA-Gw
- the AAA-Gw returns with a timeout to SCP (i.e. the stop-accounting opcode call hasn't returned within the configured timeout)
- the opcode hasn't left a trace on DB, as if the DB commit was missing
- no error is found in either the 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-Gw, but with the corresponding event found on DB.
How can we explain the "missing commit" events and how can we minimize them?
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