vTIPS #2 – Resetting VIN Database

VMware Infrastructure Navigator or vRealize Infrastructure Navigator as its now called, is a very light weight and very simple to use and rarely has an issue. but occasionally like everything problems come up. like “access failed. an unknown VM access error has occurred” generally its easier to just redeploy but here is a tip you can redeploy without redeploying with a couple of simple commands.

1) log onto the VIN server as root
2) run the command :
monit stop vadm-engine

This will stop the VIN service

3) execute the file /opt/vadm-db-config/bin/drop_db.sh

This will drop the VIN database

4) execute the file /opt/vadm-db-config/bin/update_db.sh

This will re configure the database

5) run the command:
monit start vadm-engine

This will start the VIN service.

The appliance should then start preparing the environment.

Another good command to run is monit summary this will show the service status.

Cheers

3 thoughts on “vTIPS #2 – Resetting VIN Database

  1. VMware should pay you for this information. Not even their own documentation tells you how to do this (typical of late).

    • Cheers for the kind words,

      Your right, documentation is thin on the more advanced features these days. I find anything that involves blowing away databases they prefer a support ticket to dish out that kind of information. I have a similar one for vCOps 5.x with removing vCenters.

      Would still be nice to be easily find these in official doco to at least know they exist and use t own risk type of disclaimer

  2. Pingback: Resetting VMware vRealize Infrastructure Navigator database | VMware Admin's Blog

Leave a Reply

Your email address will not be published. Required fields are marked *

*

Anti SPAM BOT Question * Time limit is exhausted. Please reload CAPTCHA.