ProcTime Instrumentation For Dm_timos Memory Leakage
Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 184.108.40.206.0
Information in this document applies to any platform.
***Checked for relevance on 12-Oct-2011***
DM_TIMOS memory usage rises while rating non-session traffic. As there is no session traffic, no
transient objects are present and the timos memory usage should be constant.
Steps to Reproduce
1. Setup timos to migrate data at startup, to be sure that no further migration takes place
[setting 'DataMigrationOnStartup = true' in timos registry]
2. Create an account.
3. Rate high amount of non-session traffic on this account.
Observation is about ~200 MB increase per ~20000 SMS. Possibly DM_TIMOS memory is leaking.
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