Duplicate groups are seen from Data Sources integrated with Performance Management.
This is often observed after a Data Source is deleted and added again to Performance Management.
The duplicates of the groups are coming from Performance Management. They are contained in the Data Source Orphan Groups list. To see that that list is found on the Manage Groups page via Administration->Group Settings->Groups.
Once on the Manage Groups page select:
This can be seen for the following Data Sources:
All supported Performance Management releases
At some point the NFA Data Source was deleted from Performance Management then added back again.
When a Data Source is deleted, Performance Management does not remove the Groups. Instead it moves them into a Data Source Orphan Groups list. Once NFA is added again and re-integrated with Performance Management the group was synchronized to Performance Management a second time.
The end result is two instances of the Group. One is a working version of the group and one which is orphaned.
To resolve this we will remove the Groups that are orphaned to ensure there is only one instance of the Group showing in Performance Management.
In the Manage Groups page go to the Orphan Groups list and delete all present.
NOTE: The 'Data Source Orphan Groups' Group will only be visible in the Group section of the UI if the system does in fact have orphaned groups due to an originating data source having been removed. If it is not present, no cleanup via Group deletion is required.
In the Manage Groups page to the Data Sources User Defined Groups and delete all present.
These sync failure messages can be related with this Duplicate groups:
PC DM message:
INFO | jvm 1 | AAAA/MM/DD hh:mm:ss | ERROR | pool-3-thread-9 | AAAA/MM/DD hh:mm:ss,651 | com.ca.im.portal.dm.productsync.DataSourcePoller
INFO | jvm 1 | AAAA/MM/DD hh:mm:ss | |
INFO | jvm 1 | AAAA/MM/DD hh:mm:ss | Data source DS(22) Network Flow [email protected] 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:
INFO | jvm 1 | AAAA/MM/DD hh:mm:ss | javax.xml.ws.soap.SOAPFaultException: Server was unable to process request. ---> Exception has been thrown by the target of an invocation. ---> Flatten failed on Interface ---> Flatten failed on Interface ---> Circular reference found in group relations.
…
INFO | jvm 1 | AAAA/MM/DD hh:mm:ss | Caused by: org.apache.cxf.binding.soap.SoapFault: Server was unable to process request. ---> Exception has been thrown by the target of an invocation. ---> Flatten failed on Interface ---> Flatten failed on Interface ---> Circular reference found in group relations.
NFA Message
H:MM:SS 1 - CallMethod.Invoke - :
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> NetQoS.ReporterAnalyzer.i18n.i18nException: Flatten failed on Interface ---> NetQoS.ReporterAnalyzer.i18n.i18nException: Flatten failed on Interface ---> NetQoS.ReporterAnalyzer.i18n.i18nArgumentException: Circular reference found in group relations.
at NetQoS.ReporterAnalyzer.Data.ReporterAnalyzer.ProductSync.PushedMembersDc.Flatten(String typeTable, String itemTypeName, UInt32 startTime, Boolean removeInheritance)
Resolution
Remove all entries in All Interfaces (Groups->Inventory->Data Sources)
Delete the "Data Source Orphan Groups" group (Groups->Inventory->Data Sources)
Perform NFA full resync
Recycled the PC services