After several months of working with this, I wish I could add something substantive, but after watching over this posts for a few months, I just want to throw in and say I have the same problem. All sorts of tweaking, attempts, switching, have all come up empty.
The funny thing is I can deploy this image on my Mac's VMWare Fusion 6, and my Window's VMWare Workstation with *no* trouble. It literally is plug and play like its supposed to be (on Fusion I have to go to /opt/vmware/share/vami/vami_config_net after first startup to set the Network interface).
I am absurdly stumped why this product seems to randomly work and fail. The only thing this VCSA appliance *doesn't* work on is the primary VM Host I need it to work on. Keep in mind that we're talking identical environments. They all are on the same network, under the same internal domain, under the same NTP server, and using the same internal DNS servers. It works on VMWare Fusion, VMWare Workstation, and I was even able to shoehorn it onto my XenServer 6.2 host. But my singular ESXi 5.5 host refuses to run it with this same Database schema failure every single time. Keep in mind I've completely reinstalled the Hypervisor several times over, and in fact, the past few day's tests have been on a host with no special customization at all aside from Network configuration. No external Storage, Read Caches, Sites, VLANs, or anything. I've reset and unit tested just about everything on this host with absolutely nothing showing issue *except* this Appliance.
This has been a profoundly experience for months now as I essentially have no benefits of using 5.5 due to VMWare leveraging the use of the vCenter Web Client. Really wish I could get a breakthrough on this but after over a month of trying back when 5.5a was out and with the same issue in 5.5b, I'm not holding out much hope. If I get any sort of resolution, I will certainly update this post.