ACS Customer Profile is Corrupted During Edit via SMS Screens
Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Communications Network Charging and Control - Version 2.4.0 to 4.4.1 [Release 2.4 to 4.4]
Information in this document applies to any platform.
An ACS (Advanced Control Services) customer profile becomes corrupted after saving changes to the Number Translation lists or Termination Number Ranges via the SMS (Service Management Server) Screens.
At the time of the corruption these conditions may also occur:
- SMS Screens become unresponsive for a short period as the save that causes the corruption is done.
- Other SMS Screens sessions may also become unresponsive attempting to access the same ACS customer profile.
After the corruption all attempts to access the profile result in errors on the Java console (if visible). You may see errors like these:
com.g8labs.common.utils.CorruptProfileBlockException: offset >= length
This corrupt data is replicated successfully to all applicable nodes and the SLC (Service Logic Controller, also called UAS or SCP) may be able to read some of the profile and process a subset of the expected number translations correctly.
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