When attempting to add NFA to NPC/CAPC, you may run into a bind failure like this:
From CAPC/NPC DMService log:
Data source Network Flow [email protected]_nfa.ca.com encountered an error while processing a sync request. The problem is in the data source, not CAPC. Check the logs for the data source to determine the cause of the problem. The following stack trace shows the context of the sync request:
java.lang.IllegalArgumentException: Data source x is reporting x group self-reference(s).
at com.ca.im.portal.dm.productsync.DataSourceBind.bindGroupMembers(DataSourceBind.java:1136)
at com.ca.im.portal.dm.productsync.DataSourceBind.processBindingTables(DataSourceBind.java:187)
at com.ca.im.portal.dm.productsync.DataSourceBind.bind(DataSourceBind.java:102)
at com.ca.im.portal.dm.productsync.DataSourceBindPhase.executeInternal(DataSourceBindPhase.java:55)
at com.ca.im.portal.dm.productsync.DataSourceSyncPhase.execute(DataSourceSyncPhase.java:95)
at com.ca.im.portal.dm.productsync.BindSyncPhaseTask.execute(BindSyncPhaseTask.java:78)
at com.ca.im.portal.dm.productsync.SyncPhaseExecutor$MakeDSSyncPhaseCallable$1.call(SyncPhaseExecutor.java:120)
at com.ca.im.portal.dm.productsync.SyncPhaseExecutor$MakeDSSyncPhaseCallable$1.call(SyncPhaseExecutor.java:113)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
This NFA instance was most likely added to another Performance Center at one point in time and the leftover groups are causing an issue.
**Before making changes we ask that you backup the reporter and netqosportal databases.**
First we will need to locate the group that has a self-reference in CAPC/NPC.
The amount of rows returned should also match the amount of self-references in the bind failure error log. Now we need to remove them.