My Oracle Support Banner

ACS Customer Profile is Corrupted During Edit via SMS Screens (Doc ID 1326354.1)

Last updated on FEBRUARY 22, 2019

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.

Symptoms

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:

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.<HOSTNAME>.common.utils.CorruptProfileBlockException: offset >= length

 

java.lang.ArrayIndexOutOfBoundsException:

 

Note: See <note 452853.1> for instructions on how to enable the java console.



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.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 Restoring The Data
 1. Check the undo retention
 2. Identify the ID of the corrupted customer profile
 3. Get the profile information
 4. Check for the last update of the data for the customer profile
 5. Extract the old profile using the Java tool
 6. Check the profile structure
 7. Write the profile to the database
 8. Check that the profile has updated correctly
 Avoiding Profile Corruption
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.