Profile Date Store Node Fails To Create A New Field in a Subscriber's Profile

(Doc ID 1468084.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.

Symptoms

After the upgrade to 4.4.1.0.0, when using a Profile Date Store (PDS) Feature Node against a subscriber's profile block that does not have such a field, it fails with the following error:

If the subscriber does already have this field set in their profile block it is successful.

 

More information about the Profile Date Store Feature Node:

  Takes the current system date and extends it by the Date Extension number configured in the node. The extended date is stored within the requested profile, for future use. If a Date Extension is not specified, then the current system date is stored.

 

Changes

Upgrade to Galaxy v4.4.1.
Additional interim fix for the PMS library:
449133326 1110564 ../../PMS/lib/libpmsMacroNodes.so
449133326 1110564 ../../PMS/lib/libpmsMacroNodes.so.13727684 

Cause

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