The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)
View by Article ID
vCloud Usage Meter collections fail after an upgrade (2044841)
Symptoms
After upgrading from vCloud Usage Meter 2.3.0 to 2.3.2 or 3.0, you experience these symptoms:
Collections against vCenter Server fail
In the user interface and the um.log file, you see an error similar to:
A collection from 10.21.11.202, begun at 2013-02-04 09:35:01, failed at 2013-02-04 09:35:24. java.sql.BatchUpdateException: Batch entry 0 insert into "Sample" ("id", "vmId", "collectionId", "vmMemSize", "vmBillingMemory") values (nextval('"s_Sample_id"'),'360','11659','4096','2048') was aborted. Call getNextException to see the cause.
Cause
This issue occurs when upgrading directly from vCloud Usage Meter 2.3.0 to 2.3.2 or 3.0.
When vCloud Usage Meter is upgraded from 2.3.0 to 2.3.1, specific columns in the Sample table are removed, which does not occur when you upgrade directly to 2.3.2 or 3.0.
Resolution
If the upgrade from 2.3.0 to 2.3.1 is skipped and vCloud Usage Meter is upgraded directly to 2.3.2 or 3.0, you must manually run the 2.3.0 to 2.3.1 database upgrade script.
To manually run this script:
Log in to the vCloud Usage Meter virtual machine as root.
Note: The default password is vmware.
Run this command to rerun the 2.3.0 to 2.3.1 database upgrade script:
su - postgres -c "psql -d usage_meter_db -f '/opt/vmware/cloudusagemetering/database/migrate/230-231.sql'"
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.
