CRJAZ1992E The "com.ibm.team.repository.ClusterScopedDiagnosticTask"
Accepted answer
Hi Mohan,
If this is just a cluster diagnostic, you can ignore it, as if environment is not clustered.
The diagnostic service error is not impacting CLM performance or functionality. The diagnostic just fails to run because of the duplicate result. However, because this diagnostic is not running, if there is ever a problem in the related area (com.ibm.team.repository.service.diagnostics.basic.internal.dbLockCounte rContentServiceDiagnostic), it will go unnoticed. Or more specifically, you will never get a file with counter data.
This is due to some condition introduced in earlier version of CLM support 4.X for clustering.
Regards,
Arun.