Setting Expiration Time In Transient Objects Manager In Timos Is Not Possible. (Doc ID 1216683.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

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

Goal

Need to levarage BRM capability of automatic, delayed /active_session removing from timos memory.
The required value for time gap between /active_session closing and removing it is 6 hours.

However, TIMOS ignores the configuration and doesn't allow for 6h hours of expiration. It always uses value of 480sec, which is to low to meet business requirements for duplicate check.

What is the recommendation?

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