This article explains the complete steps to Reset vCenter Inventory Service Database in vSphere 5.5 environment. Running out of space in the vCenter Server installation partition can cause the inventory database corruption and we might need to reset this inventory server database.
Symptoms were something similar to non-responsive vCenter server and after a server reboot vCenter was not connecting to the network and services or any other consoles were unable to open to check the status. I was ended up with the same situation with couple of my clients and I thought to write this article for anyone who wants to follow and reset vCenter Inventory Service database easily.
Actual, Server response was really bad when I logged in to the vCenter Server from the console. Network was disconnected and I was not able to open the Network Settings of the server.
So, the next step was something that optional as I usually follow in similar situations, I restarted the server and entered to the “Safe Mode” of the vCenter Server. Set all the VMware services to manual mode to avoid this non-responsive situation of the server. (Screen capture only shows the VMware VirtualCenter Server service and VMware VirtualCenter Management Web Services, all the services should be in the manual mode in order to get the full response state).
I rebooted the Server again and logged in to the server, and navigate to “C:\Program Files\VMware\Infrastructure\Inventory Service\data” location and identify the “xdb.bootstrap” file
Opened the command prompt with “Run As Administrator” and navigated to the above location, and executed the below command to extract the bootstrap header to a text file.
type "C:\Program Files\VMware\Infrastructure\Inventory Service\data\xdb.bootstrap"|findstr "<server" > "C:\Program Files\VMware\Infrastructure\Inventory Service\datahash1234321.txt"
See below output
Navigated to the location of the output file as mentioned in the above command and check whether the file has been created as we expected
File output would be something similar to this
Renamed the data folder as “data.old” which is under “C:\Program Files\VMware\Infrastructure\Inventory Service”
Navigated to the “C:\Program Files\VMware\Infrastructure\Inventory Service\scripts” location and executed the “createDB.bat” file
I let that script to do the rest
If this operation has been successfully completed then new “data” folder should be there as below in the screen capture
Opened the Notepad with “Run As Administrator” privileges and opened the new “xdb.bootstrap” file
Copied the content of the extracted header file and pasted it in the newly created file as below
Restarted the Inventory Service
Changed the directory to the “C:\Program Files\VMware\Infrastructure\VirtualCenter Server\isregtool” location in the command prompt
Run the below command with the server FQDN and rhe relevant ports of the lookup service
register-is.bat https://<SERVER_FQDN>:443/sdk https://<SERVER_FQDN>:10443 https://<SERVER_FQDN>:7444/lookupservice/sdk
Command should end up with similar output like this
Restarted the services after that and issue has been fixed. Make sure to set the service start type to “Automatic” and “Delayed Start” (VMware VirtualCenter and VMware VirtualCenter Management WebServices)
If you found this post as useful please rate the post and share it!