This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Capacity Optimization
TrueSight Capacity Optimization 20.02, 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0 ; BMC Performance Assurance for Servers 9.5
When running a Process Existing Data Manager run the following error is being generated for all nodes:
best1analyze-W-DATAERROR, Repository path
/usr/adm/best1_default/collect/[hostname] not visible for computer [hostname].
Another version of this error is:
best1analyze-W-DATAERROR, No required metric groups in repository /usr/adm/best1_default/collect/[hostname]/noInstance/Mmm-dd-yyyy.hh.mm for computer [computer].
TrueSight Capacity Optimization (Gateway Server) 20.02, 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0
BMC Performance Assurance for Servers 9.5, 9.0
TSCO Gateway Server/BMC Performance Assurance (BPA) console
This first thing to check is if the UDR data from the target processing date(s) exists in the /usr/adm/best1_default/collect directory (the directory specified in the error message, which may be different in your environment) on the console. If the directory specified is the /usr/adm/best1_default/collect directory that is a symbolic link that usually points to the true data repository on the console. If you have recently upgraded the Perform console version, one possibility is that it has changed by the upgrade to point to a new repository which would cause the new console to not be able to find the previously collected data (because it actually exists in a different directory on the machine).
The "best1analyze-W-DATAERROR, No required metric groups in repository /usr/adm/best1_default/collect/[hostname]/noInstance/Mmm-dd-yyyy.hh.mm for computer [computer]." message means that the /usr/adm/best1_default/collect/[hostname]/noInstance/Mmm-dd-yyyy.hh.mm directory exists on the machine but doesn't contain one of the required metric groups for data processing.
So, if processing data from a Unix machine it is likely that either the System_Configuration or Cpu_Statistics group is missing from the UDR data on the console. If processing data from a Windows machine it is likely that either the NT_System_Configuration or NT_CPU_Statistics group is missing from the UDR data on the console.
Another scenario you may see is that the Mmm-dd-yyyy.hh.mm directory mentioned in the error message is not related to the time interval of data that you have requested to process. In that scenario that means that either:
- The /usr/adm/best1_default/collect/[hostname]/noInstance/[Target Date] directory doesn't exist on the machine
-- or --
- The /usr/adm/best1_default/collect/[hostname]/noInstance/[Target Date] doesn't contain the required metric groups.
If the problem is related to data missing on the console the next step would be to obtain the log files from the remote node. See 000090065: Truesight Capacity Otimization (TSCO) : Capturing the Capacity Agent collection log files from the remote node - INCLUDES VIDEO (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000090065), for more information on that.