Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

vCenter Chargeback Manager 2.5 Patch 01 (2041041)

Details

In a vCenter Chargeback Manager 2.5 setup, you might see the  following issues:
  • The System Health tab shows the vCenter Chargeback  Manager Data Collector is down.
    Although the data collector services are running and the databases  are up and running, the data collector status  is shown as  down in the System Health tab. This issue happens when the Hosts and Clusters & VMs and Templates job fails. The data collector log file  contains an error similar to the following:
    ERROR [(2) HostsClustersAndVMTemplatesInventorySyncJob on VC 845] [job.AbstractInventorySyncJob] 0250: Unable to update information in the database.
    <Response> 
       <Error majorErrorCode="404" minorErrorCode="177" message="Unable to update information in the database."/>
    </Response>
        at  com.vmware.vim.vcenter.das.dao.impl.HibernateVCenterBaseDAOImpl.saveOrUpdate(HibernateVCenterBaseDAOImpl.java:284)
        at  com.vmware.vim.vcenter.chargeback.dao.impl.HibernateVcEntityRelationDAOImpl.saveOrUpdate(HibernateVcEntityRelationDAOImpl.java:177)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryHistoryManagerImpl$3$1.executeInternal(InventoryHistoryManagerImpl.java:255)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryHistoryManagerImpl$3$1.executeInternal(InventoryHistoryManagerImpl.java:246)
        at  com.vmware.vim.vcenter.chargeback.lock.vcconfig.VCenterServerLockUtils$VCenterServerDBLock.executeWithWlock(VCenterServerLockUtils.java:159)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryHistoryManagerImpl$3.executeInternal(InventoryHistoryManagerImpl.java:246)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryHistoryManagerImpl$3.executeInternal(InventoryHistoryManagerImpl.java:242)
        at  com.vmware.vim.vcenter.das.utils.DBTransaction.execute(DBTransaction.java:65)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryHistoryManagerImpl.applyUpdates(InventoryHistoryManagerImpl.java:242)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryConstructionAgentImpl.createOrRepairInitialInventoryForView(InventoryConstructionAgentImpl.java:509)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryConstructionAgentImpl.createOrRepairInitialInventory(InventoryConstructionAgentImpl.java:418)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryConstructionAgentImpl.fetchInventory(InventoryConstructionAgentImpl.java:338)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryConstructionAgentImpl.fetchInventory(InventoryConstructionAgentImpl.java:308)
        at  com.vmware.vim.vcenter.datacollector.inv.manager.impl.InventoryConstructionAgentImpl.trackInventory(InventoryConstructionAgentImpl.java:291)
        at  com.vmware.vim.vcenter.datacollector.job.AbstractInventorySyncJob.run(AbstractInventorySyncJob.java:28)
    Caused by: org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [com.vmware.vim.vcenter.chargeback.dto.CbVcEntityRelation#com.vmware.vim.vcenter.chargeback.dto.CbVcEntityRelationId@14d9d84]
    ...

  • The external network usage for both upload and download is  reported as zero and, therefore, the corresponding cost is reported  as zero.

Solution

To address these issues, you must download the JAR files attached to this KB article and perform the steps mentioned in the following sections.
 
Resolving the vCenter Chargeback Manager Data Collector down  status issue
  1. Download the vcenter-cbm-core-vc-dc-2.5-GA.jar file  from this KB article.
  2. Stop the load balancer service and all the vCenter Chargeback  Manager and corresponding data collector services, including vCloud  Director data collector and vShield Manager data collector  services.
  3. Take a backup of the vCenter Chargeback Manager database.
  4. For each vCenter Chargeback Manager server in your setup,  perform the following steps:
    1. Go to the  <CHARGEBACK_HOME>\apache-tomcat\webapps\vCenter-CB\WEB-INF\lib  folder. (For example; C:\Program Files\VMware\VMware vCenter Chargeback\apache-tomcat\webapps\vCenter-CB\WEB-INF\lib).
    2. Copy the vcenter-cbm-core-vc-dc-2.5-GA.jar file from  the lib folder to a different folder, say  C:\CBM_backup\CBMServer.
    3. Replace the JAR file in the lib folder with the JAR  file (with the same name) downloaded from this KB article.
    In a cluster installation, these steps must be performed for each  vCenter Chargeback Manager instance in the cluster.
  5. For each vCenter Chargeback Manager Data Collector in your  setup, perform the following steps:
    1. Go to the <CHARGEBACK_DATACOLLECTOR_HOME>\lib  folder. (For example; C:\Program Files\VMware\VMware vCenter Chargeback\DataCollector-Embedded\lib).
    2. Copy the vcenter-cbm-core-vc-dc-2.5-GA.jar file from  the lib folder to a different folder, say  C:\CBM_backup\CBMDataCollector.
    3. Replace the JAR file in the lib folder with the JAR  file (with the same name) downloaded from this KB article.
    You must perform these steps for each vCenter Chargeback Manager  Data Collector that you have installed in your setup.
  6. For each vCloud Director Data Collector in your setup, perform  the following steps:
    1. Go to the  <VCLOUD_DIRECTOR_DATACOLLECTOR_HOME>\lib  folder. (For example; C:\Program Files\VMware\VMware vCenter Chargeback\VMware Cloud Director DataCollector-Embedded\lib).
    2. Copy the vcenter-cbm-core-vc-dc-2.5-GA.jar file from  the lib folder to a different folder, say  C:\CBM_backup\CloudDataCollector.
    3. Replace the JAR file in the lib folder with the JAR  file (with the same name) downloaded from this KB article.
    You must perform these steps for each vCloud Director Data  Collector that you have installed in your setup.
  7. For each vShield Manager Data Collector in your setup, perform the following steps:
    1. Go to the  <VSHIELD_MANAGER_DATACOLLECTOR_HOME>\lib folder.  (For example; C:\Program Files\VMware\VMware vCenter Chargeback\vShield Manager DataCollector-Embedded\lib).
    2. Copy the vcenter-cbm-core-vc-dc-2.5-GA.jar file from  the lib folder to a different folder, say C:\CBM_backup\VSMDataCollector.
    3. Replace the JAR file in the lib folder with the JAR  file (with the same name) downloaded from this KB article.
    You must perform these steps for each vShield Manager Data  Collector that you have installed in your setup.
  8. Start the load balancer service and all the vCenter Chargeback Manager and corresponding data collector services.

Resolving the external network usage reported as zero  issue
  1. Download the vcenter-cbm-integration-vsm-2.5-GA.jar  file from this KB article.
  2. Stop the load balancer service and all the vCenter Chargeback  Manager and corresponding data collector services, including vCloud  Director data collector and vShield Manager data collector  services.
  3. Take a backup of the vCenter Chargeback Manager database.
  4. Go to the  <VSHIELD_MANAGER_DATACOLLECTOR_HOME>\lib folder.  (For example; C:\Program Files\VMware\VMware vCenter Chargeback\vShield Manager DataCollector-Embedded\lib)
  5. Copy the vcenter-cbm-integration-vsm-2.5-GA.jar file  from the lib folder to a different folder, say  C:\CBM_backup\VSMDataCollector.
  6. Replace the JAR file in the lib folder with the JAR  file (with the same name) downloaded from this KB article.
  7. Clear all the External Network stats from the vCenter Chargeback Manager database by running the following SQL query on  the database
    • For a new vCenter Chargeback Manager installation:
       
      DELETE FROM CB_CUSTOM_COUNTER_PERF_STAT WHERE RESOURCE_ID  in
         (SELECT COMPUTING_RESOURCE_ID FROM  CB_COMPUTING_RESOURCE WHERE COMPUTING_RESOURCE_NAME in ('External Network Transmit' ,'External Network Receive'));
       
    • For an upgraded vCenter Chargeback Manager setup, run the  following SQL query for each IP address that is synced for the  first time in vCenter Chargeback Manager after upgrade. Ensure that  you replace XYZ_IPADDRESS with the IP address name in  X.X.X.X/32 format. For example; IP address name format is 10.111.60.200/32.
       
      DELETE FROM CB_CUSTOM_COUNTER_PERF_STAT WHERE RESOURCE_ID  in
         (SELECT COMPUTING_RESOURCE_ID FROM  CB_COMPUTING_RESOURCE WHERE COMPUTING_RESOURCE_NAME in ('External Network Transmit' ,'External Network Receive')) and ENTITY_ID  in
            (SELECT CB_HIERARCHICAL_ENTITY_ID  FROM CB_HIERARCHICAL_ENTITY WHERE ENTITY_ID in
               (SELECT ENTITY_ID  FROM CB_ENTITY WHERE ENTITY_NAME LIKE  'XYZ_IPADDRESS'));
       
    NOTE: If the vCenter Chargeback Manager database is an  ORACLE database, ensure that you commit the changes.
  8. Start the load balancer service and all the vCenter Chargeback  Manager and corresponding data collector services. Wait for two or three  cycles of external network stats to be synchronized by the vShield Manager  Data Collector. This might take approximately 15 minutes.

Attachments

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 4 Ratings
Actions
KB: