Recently a vCloud environment I was working in was unable to provision any VMs. The vcloud-container-debug.log had the following relevant entries:
2015-03-26 14:05:20,424 | ERROR | backend-activity-pool-16 | JDBCExceptionReporter | Data truncation | vcd=4c14b291-7ca6-4697-8127-838e6768c1e3,task=6ce4e6a8-33d5-4eaa-ae26-ced099fbcd34 activity=urn:uuid:6ce4e6a8-33d5-4eaa-ae26-ced099fbcd34
2015-03-26 14:05:20,424 | ERROR | backend-activity-pool-16 | JDBCExceptionReporter | Arithmetic overflow error converting expression to data type int. | vcd=4c14b291-7ca6-4697-8127-838e6768c1e3,task=6ce4e6a8-33d5-4eaa-ae26-ced099fbcd34 activity=urn:uuid:6ce4e6a8-33d5-4eaa-ae26-ced099fbcd34
After working with VMware support, it was determined that the cause of this was a disconnected datastore that was reporting an available size "in the exabytes". VMware support analyzed the VCD database to determine this. The environment was also using the *Any* storage policy. But even when that policy was no longer being presented, provisioning still failed with the same error.
The resolution was to remove the disconnected datastore and provisioning completed successfully.
This involved a lengthy resolution process, so I wanted to take the time to share the findings should someone else ever run in to this one.