MGMT/NSP Datafeed "Apply Changes" is Returning the Error : "configuration changes couldn't be synchronized to IXP subsystem"

Asset ID:	1-72-2159910.1
Update Date:	2018-01-31
Keywords:

Solution Type Problem Resolution Sure

Solution 2159910.1 : MGMT/NSP Datafeed "Apply Changes" is Returning the Error : "configuration changes couldn't be synchronized to IXP subsystem"

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.0 and later
Information in this document applies to any platform.

Symptoms

In NSP Datafeed application, the GUI is displaying a banner telling the user that "Configuration changed, changes need to be applied", and when clicking on the "Apply Changes" button a pop-up is displayed with following error:

configuration changes couldn't be synchronized to IXP subsystem

/var/log/nsp/weblogic/nsp/application.log is displaying the following error:

duplicate key in table DECfgLink

Changes

This error occurs after synchronizing an IMF subsystem and discovering/updating network elements in NSP CCM.

Cause

DECfgLink is an oracle view that is used by DataFeed to map the real link name in the Datafeed export files and it cannot contain duplicate values.

Solution

To find the duplicate link ask the help of Oracle Support and mention this document reference.

As an Example the duplicate link will be called "my_dup_link".

That oracle view is built from CFG_LINK table where the LINK_ID is constraint to be unique so only the LINK_NAME can be duplicated.

To fix the issue you need to search for duplicate LINK_NAME in CFG_LINK oracle table. this can be done with the following sql query :

SQL> select LINK_NAME from CFG_LINK group by LINK_NAME having count(*) > 1;
LINK_NAME
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
my_dup_link

So the link called "my_dup_link" is duplicated and causing the issue.

Note that there may be more than one link.

To fix the issue the following steps have to be applied:

Open NSP CCM GUI and search for Links named "my_dup_link" in the "Network Elements"
Delete the duplicated links
Apply changes on the subsystems that were impacted by the deletion
Synchronize the subsystems that were impacted by the deletion (the duplicate link should be discovered only once)
Apply Changes with NSP Datafeed, this time there should be no errors

Attachments

This solution has no attachment