If I go in to view performance stats for a host or VM in VC2 it just comes up with "Performance data is currently not available for this entity".
In VC1 it used to log the data and display it fine.
Any ideas?
We had the same issue, we're using oracle on AIX, we tried what support suggested:
"I would suggest attempting to truncating the tables again if VPX_SAMPLE_TIME1
was missed. Can you perform a backup of the database in case we need to refer
back to it later on?
We should stop the VC service, then truncate the following:
VPX_SAMPLE
VPX_SAMPLE_TIME1
VPX_SAMPLE_TIME2
VPX_SAMPLE_TIME3
VPX_SAMPLE_TIME4
VPX_HIST_STAT
VPX_HIST_STAT1
VPX_HIST_STAT2
VPX_HIST_STAT3
VPX_HIST_STAT4"
This didn't buy us anything. In the end our Oracle DB had the Job Queue Processes set to 0 on the db, once we set this to 2 we stopped the VC services, trunc'd the above tables, started the service and than problem solved.
Matt~
I had this problem on an ESX 3.5 host with VC 2.5 saying "Performance data is currently not available for this entity".
Fixed the problem by logging onto the ESX host itself and running:
service mgmt-vmware restart
Roland.
This tripped me up too. You need to make sure (on sql2000 at least) that SQLAGENTSERVCE is running and set to auto start. Without that the SQL rollup jobs to collapse day->week->month wont run and even though you are logging data you cant access it. Support walked me through this and that minor change cured everythihng. I would have thought that service would be autostarted by default, but I'm not a SQL guru. Also in VC config turn up client connection timeout to 120, this allows the program more time to gather the requested data, otherwise you will get this same error while its trying to generate the graphs.
Hope this helps!