Happy Friday evening y’all. Tonight’s blog post comes from a former colleague of mine whom I will call “Paul Berg”. Paul came across an error in VMware vSphere which he was able to resolve and he would like to share the solution with the VMware community.
Paul uses an Oracle database to back end vCenter. When viewing the performance charts in Performance tab | Overview button, he received the following error:
Perf Charts service experienced an internal error.
Message: Report application initialization is not completed successfully. Retry in 60 seconds.
You can probably guess what followed… missing data in the charts. No joy whatsoever.
Following is the resolution:
1. Get the fully qualified domain name or the global name of the TNS service from the Oracle database. This can be found in the file named tnsnames.ora on the Oracle database server
2. Add this FQDN to the registry key HKLM\Software\ODBC\ODBC.INI\VirtualCenter\ServerName on the VC server.
3. Restart the VMware VirtualCenter Server service.
For us, the database was listed as VMDB in the registry. We have moved to an Oracle RAC configuration so I needed to change the entry to VMDB.GLOBAL to match what was in the tnsnames.ora listing. I wasn’t aware that VMDB.GLOBAL was considered the FQDN for an Oracle DB.
The following VMware KB Article 1012812 documents the issue as well as a few different approaches to a resolution depending on root cause. Again, this issue is specific to Oracle database environments.
Performance Overview charts fail with the error: STATs Report Service internal error
Thank you for sharing Paul. I’ve got one more in the queue from you – I’ll try to get it out in the next couple of weeks. Here’s a teaser: Poor vSphere performance on Nehalem processors. Ouch!
I like the use of “y’all!” Hopefully you are fixin’ to help spread that term around your parts of Minnesota?
Tell your Mom and them I said Hi!